Triple
T15323259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Coliseum |
E366346
|
entity |
| Predicate | redevelopedUse |
P63843
|
FINISHED |
| Object | office space |
—
|
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: office space | Statement: [Washington Coliseum, redevelopedUse, office space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redevelopedUse Context triple: [Washington Coliseum, redevelopedUse, office space]
-
A.
redevelopmentFor
Indicates a relationship where one entity is intended, designated, or used for the redevelopment of another entity.
-
B.
redevelopedAfter
Indicates that one entity was redeveloped at a later time than, and as a subsequent phase or replacement to, another entity.
-
C.
redevelopmentTo
chosen
Indicates a transformation relationship where one entity is redeveloped, converted, or repurposed into another entity.
-
D.
redevelopmentFrom
Indicates that one entity is created or transformed as a result of redeveloping or repurposing another pre-existing entity.
-
E.
reopenedAfterRedevelopment
Indicates that a place or facility was closed for redevelopment and subsequently opened again once the redevelopment was completed.
- 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_69d85a121520819093dcce999fdefe1a |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03dd5ce0c819093c9a14de549dff6 |
completed | April 16, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.