Triple
T29414723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Station (Providence, Rhode Island) |
E745993
|
entity |
| Predicate | postFireUse |
P167154
|
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: [Union Station (Providence, Rhode Island), postFireUse, office space]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postFireUse Context triple: [Union Station (Providence, Rhode Island), postFireUse, office space]
-
A.
postUse
Indicates that one entity is used or occurs after another entity has been used or has taken place.
-
B.
fireUse
Indicates the use or application of fire by one entity on, with, or for another entity or object.
-
C.
postConquestUse
Indicates how something is used, occupied, or functionally repurposed after a conquest has taken place.
-
D.
postExpulsionUse
Indicates the use or treatment of something after it has been expelled, removed, or discharged from its original context or container.
-
E.
useAfterDamage
Indicates that an entity is used or applied only after damage has occurred to another entity or object.
- F. None of above. chosen
Provenance (4 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 28, 2026, 3 p.m.