Triple
T3251953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ishtar Gate |
E68201
|
entity |
| Predicate | guardedEntranceTo |
P46861
|
FINISHED |
| Object | inner city of Babylon |
—
|
LITERAL 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: inner city of Babylon | Statement: [Ishtar Gate, guardedEntranceTo, inner city of Babylon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardedEntranceTo Context triple: [Ishtar Gate, guardedEntranceTo, inner city of Babylon]
-
A.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
B.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
C.
hasLandmarkAtEntrance
Indicates that a specific landmark is located at or directly adjacent to the entrance of something.
-
D.
hasEntranceControl
Indicates that an entity implements or is subject to mechanisms that regulate or control access to its entrance.
-
E.
entranceMarkedBy
Indicates that the entrance of one entity is distinguished or identified by the presence of another entity (such as a sign, marker, or feature).
- F. None of above. chosen
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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf425394819084ae6304da211c00 |
completed | March 8, 2026, 5:17 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada525bb2c8190b773efe6d696b6ab |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:09 p.m.