Triple
T35059866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nahal Iron |
E1011563
|
entity |
| Predicate | nearArchaeologicalSites |
P14422
|
FINISHED |
| Object | Tel Megiddo area |
E1546264
|
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 Megiddo area | Statement: [Nahal Iron, nearArchaeologicalSites, Tel Megiddo area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearArchaeologicalSites Context triple: [Nahal Iron, nearArchaeologicalSites, Tel Megiddo area]
-
A.
hasNearbyArchaeologicalSite
chosen
Indicates that an entity is located close to or in the vicinity of an archaeological site.
-
B.
hasArchaeologicalSiteIn
Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
-
C.
hasArchaeologicalSitesFrom
Indicates that an entity contains or is associated with archaeological sites dating from a specified time period or era.
-
D.
nearbyArchaeologicalCulture
Indicates that one archaeological culture is geographically close to another archaeological culture.
-
E.
notableArchaeologicalSite
Indicates that a place is recognized as an archaeologically significant site, typically due to important historical remains, artifacts, or research findings.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78607679c819085c2e1fde23ed1ea |
completed | May 3, 2026, 5:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37cfe37a808190ae7843090f30430d |
completed | June 21, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.