Triple
T38268432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convention Center Station |
E1021133
|
entity |
| Predicate | oftenCoNamedWith |
P52939
|
FINISHED |
| Object | adjacent sports arenas |
—
|
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: adjacent sports arenas | Statement: [Convention Center Station, oftenCoNamedWith, adjacent sports arenas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenCoNamedWith Context triple: [Convention Center Station, oftenCoNamedWith, adjacent sports arenas]
-
A.
oftenNamedAfter
Indicates that one entity frequently receives its name from or in honor of another entity.
-
B.
oftenUsedAsNameFor
Indicates that something frequently serves as a name or designation for another entity.
-
C.
collectivelyKnownAs
chosen
Indicates that multiple entities are referred to together under a single shared name or designation.
-
D.
knownAsOneOf
Indicates that an entity is recognized or referred to as one member of a specified set of alternative names, labels, or identities.
-
E.
oftenRefersTo
Indicates that one entity is frequently used to mention, denote, or reference another entity in common usage or context.
- 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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:30 p.m.