Triple
T5634867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richmond Coliseum |
E147921
|
entity |
| Predicate | replacedByProject |
P29646
|
FINISHED |
| Object | Navy Hill redevelopment proposal |
—
|
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: Navy Hill redevelopment proposal | Statement: [Richmond Coliseum, replacedByProject, Navy Hill redevelopment proposal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedByProject Context triple: [Richmond Coliseum, replacedByProject, Navy Hill redevelopment proposal]
-
A.
placedBy
Indicates that one entity was positioned, set, or put in a location or context by another entity.
-
B.
replacedWith
chosen
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
C.
replacedBecause
Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
-
D.
partlyReplacedBy
Indicates that one entity has been superseded or substituted in part, but not entirely, by another entity.
-
E.
mayBeReplacedBy
Indicates that one entity can potentially be substituted or superseded by another 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0226118548190877793dadf6cacba |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.