Triple
T6964260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Istiklal Avenue |
E161446
|
entity |
| Predicate | hasPedestrianStatusSince |
P73815
|
FINISHED |
| Object | late 20th century |
—
|
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: late 20th century | Statement: [Istiklal Avenue, hasPedestrianStatusSince, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPedestrianStatusSince Context triple: [Istiklal Avenue, hasPedestrianStatusSince, late 20th century]
-
A.
hasPedestrianFunction
Indicates that an entity serves a role, purpose, or function specifically related to pedestrians or pedestrian use.
-
B.
hasPedestrianSteps
Indicates that one location or structure is connected to another by pedestrian steps or stairways.
-
C.
hasPedestrianPhase
Indicates that a traffic signal includes a dedicated phase during which pedestrians are allowed to cross.
-
D.
hasPedestrianPriority
Indicates that pedestrians are given precedence or right-of-way over other road users in a particular context or area.
-
E.
hasPedestrianSignalPattern
Indicates that there is a specific configuration or sequence of pedestrian traffic signals associated with an entity.
- 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6daf2b7bc8190a3e73f3b24f0352b |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d9bb57e88190a3a7cec34e3b617f |
completed | March 27, 2026, 7:25 p.m. |
Created at: March 27, 2026, 2:30 p.m.