Triple
T7280686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hippodrome of Constantinople |
E163136
|
entity |
| Predicate | remainsVisibleAs |
P35040
|
FINISHED |
| Object | Sultanahmet Square layout |
—
|
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: Sultanahmet Square layout | Statement: [Hippodrome of Constantinople, remainsVisibleAs, Sultanahmet Square layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remainsVisibleAs Context triple: [Hippodrome of Constantinople, remainsVisibleAs, Sultanahmet Square layout]
-
A.
visibleRemains
chosen
Indicates that some physical remnants of an entity or event can still be seen or visually detected.
-
B.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
C.
remainsLitDuring
Indicates that one entity continues to emit light or stay illuminated throughout the duration of another specified event or condition.
-
D.
visibilityDuration
Indicates the length of time for which something remains visible or observable.
-
E.
visibilityStatus
Indicates the current level or state of how observable, accessible, or exposed an entity is within a given context.
- F. None of above.
Provenance (3 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_69c6885c5964819085b209701769877f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb34fe0c8190a642fd3339f0cacd |
completed | March 27, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69c6e76c5fbc8190b378830082f11cb0 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:59 p.m.