Triple
T32022868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portland Center Stage at The Armory |
E817740
|
entity |
| Predicate | buildingRenovationType |
P42263
|
FINISHED |
| Object | adaptive reuse |
—
|
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: adaptive reuse | Statement: [Portland Center Stage at The Armory, buildingRenovationType, adaptive reuse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buildingRenovationType Context triple: [Portland Center Stage at The Armory, buildingRenovationType, adaptive reuse]
-
A.
renovationOccasion
Indicates the event, reason, or context that serves as the occasion for a renovation to take place.
-
B.
renovationFeature
Indicates that an entity has a specific renovation-related characteristic, element, or improvement associated with it.
-
C.
buildingReuseType
chosen
Indicates the manner or purpose for which an existing building is reused or repurposed.
-
D.
renovationPurpose
Indicates that an entity is being renovated with a specific intended goal, use, or outcome in mind.
-
E.
hasRenovation
Indicates that an entity has undergone, is undergoing, or is associated with a renovation process or renovation event.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:17 a.m.