Triple
T9162350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elmwood |
E219855
|
entity |
| Predicate | isOrganizedAround |
P46126
|
FINISHED |
| Object | Elmwood Avenue |
—
|
NE NERFINISHED |
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: Elmwood Avenue | Statement: [Elmwood, isOrganizedAround, Elmwood Avenue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOrganizedAround Context triple: [Elmwood, isOrganizedAround, Elmwood Avenue]
-
A.
organizedAround
chosen
Indicates that something is structured, arranged, or centered with respect to a particular focus, principle, or organizing element.
-
B.
organizedAt
Indicates that an event or activity was arranged, planned, or hosted at a specific location or venue.
-
C.
organizedAs
Indicates how elements are structured, arranged, or grouped according to a particular organizing principle or scheme.
-
D.
mayBeOrganizedBy
Indicates that an event, activity, or entity has the possibility of being organized or arranged by a particular agent or organization, without asserting that this organization definitely occurs.
-
E.
oftenOrganizedBy
Indicates that an event, activity, or process is frequently arranged, coordinated, or hosted by a particular agent or entity.
- 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_69ca83e3633c81908688a9fa2306ba99 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaa2c1a9881909b7100b6e436386d |
completed | April 1, 2026, 5:16 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:21 p.m.