Triple
T31882187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laish |
E813910
|
entity |
| Predicate | associatedWithModernSite |
P88073
|
FINISHED |
| Object | Tel Dan |
E233625
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Tel Dan | Statement: [Laish, associatedWithModernSite, Tel Dan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithModernSite Context triple: [Laish, associatedWithModernSite, Tel Dan]
-
A.
nearModernSite
Indicates that one entity is located in close physical proximity to a site or location from the modern era.
-
B.
modernSiteCorrespondsTo
chosen
Indicates that a present-day site occupies, aligns with, or directly relates to the location or extent of another (typically historical or earlier) site.
-
C.
associatedWithModernTown
Indicates that something has a defined connection or linkage to a present-day town or municipality.
-
D.
associatedSiteType
Indicates the type or category of site with which an entity is associated.
-
E.
associatedWithLegacy
Indicates that an entity has a connection or linkage to something from the past, such as historical versions, prior systems, or inherited artifacts.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e8a2a5a608190a6a0c986a6ddb1ee |
completed | June 14, 2026, 11:02 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:56 p.m.