Triple
T34732024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eaton’s College Street building |
E1001236
|
entity |
| Predicate | isRepurposedTo |
P47023
|
FINISHED |
| Object | mixed-use complex |
—
|
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: mixed-use complex | Statement: [Eaton’s College Street building, isRepurposedTo, mixed-use complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRepurposedTo Context triple: [Eaton’s College Street building, isRepurposedTo, mixed-use complex]
-
A.
laterRepurposedFor
chosen
Indicates that something was originally used for one purpose and subsequently assigned a different, new purpose.
-
B.
reusedIn
Indicates that something previously used in one context or instance is used again in another context or instance.
-
C.
isReuseOf
Indicates that one entity is derived from, or created by reusing, the content, structure, or components of another entity.
-
D.
reconvertedTo
Indicates that something has been changed back or restored to a previous state, form, or condition it once had.
-
E.
isUsedToReverse
Indicates that one entity serves the function of undoing, inverting, or changing the direction or effect of another entity or process.
- 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_69f76daf739881909ed3554f98a2b433 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.