Triple
T15793162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Javad Khan Street |
E382908
|
entity |
| Predicate | namedForHistoricalEra |
P39753
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Javad Khan Street, namedForHistoricalEra, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForHistoricalEra Context triple: [Javad Khan Street, namedForHistoricalEra, 18th century]
-
A.
historicalEraOfNaming
chosen
Indicates the historical era or time period during which an entity received its name.
-
B.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or entity.
-
C.
livedInEra
Indicates that an entity existed or was active during a particular historical era or time period.
-
D.
notableLabelEra
Indicates the historical era or time period for which a label, title, or designation is considered notable or especially relevant.
-
E.
eraOfHistoricalAssociation
Indicates the historical time period during which the association or relationship between the entities took place.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4da381c819086195e3d20591abf |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:48 a.m.