Triple
T32022867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portland Center Stage at The Armory |
E817740
|
entity |
| Predicate | typeOfBuildingOccupied |
P201907
|
FINISHED |
| Object | historic landmark |
—
|
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: historic landmark | Statement: [Portland Center Stage at The Armory, typeOfBuildingOccupied, historic landmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBuildingOccupied Context triple: [Portland Center Stage at The Armory, typeOfBuildingOccupied, historic landmark]
-
A.
typeOfBuildingSpace
Indicates the specific kind or category of building space that an entity represents or occupies.
-
B.
hasTypeOfOccupancy
Indicates that an entity is associated with a specific category or type of occupancy (e.g., residential, commercial, industrial).
-
C.
currentBuildingUse
Indicates the present functional purpose or activity for which a building is being used.
-
D.
buildingType
Indicates the specific category or function that characterizes what kind of building something is.
-
E.
intendedBuildingType
Indicates the type of building that something is planned or designed to be.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a00315632a8819092290f455babd7ee |
completed | May 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_6a002f54a0dc81909b0e54c5e110e67c |
completed | May 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_6a00315584308190abdc11e634956d42 |
completed | May 10, 2026, 7:18 a.m. |
Created at: May 1, 2026, 12:17 a.m.