Triple
T23866916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papineau Avenue |
E592606
|
entity |
| Predicate | namedForEra |
P39753
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Papineau Avenue, namedForEra, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForEra Context triple: [Papineau Avenue, namedForEra, 19th century]
-
A.
historicalEraOfNaming
chosen
Indicates the historical era or time period during which an entity received its name.
-
B.
subjectHasEra
Indicates that a subject is associated with, defined by, or belongs to a particular historical or temporal era.
-
C.
usedEraName
Indicates that an entity employed or referenced a specific historical or calendrical era name in its dating or designation.
-
D.
notableLabelEra
Indicates the historical era or time period for which a label, title, or designation is considered notable or especially relevant.
-
E.
dynasticEraName
Indicates the named historical period or era associated with a particular dynasty’s rule.
- 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cae47b40819080d1c5294ee59066 |
completed | April 29, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:13 p.m.