Triple
T37891922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourth Avenue |
E945165
|
entity |
| Predicate | hasAlternateRole |
P6239
|
FINISHED |
| Object | part of Park Avenue South route |
—
|
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: part of Park Avenue South route | Statement: [Fourth Avenue, hasAlternateRole, part of Park Avenue South route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternateRole Context triple: [Fourth Avenue, hasAlternateRole, part of Park Avenue South route]
-
A.
hasAuxiliaryRole
chosen
Indicates that an entity serves in a supporting or secondary capacity to another entity or primary role.
-
B.
hasAlternativeProfile
Indicates that an entity is associated with another profile that serves as an alternative or secondary representation of it.
-
C.
hasAlternativeReferent
Indicates that an entity can also be referred to or identified by an alternative name, label, or reference.
-
D.
hasAlternateLocation
Indicates that an entity is associated with an additional or substitute location besides its primary one.
-
E.
hasAlternateMemberType
Indicates that an entity is associated with a different or substitute type of member than its primary or standard member type.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: May 3, 2026, 4:19 p.m.