Triple
T22825513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walter De Maria Room |
E565646
|
entity |
| Predicate | permanentInstallation |
P136386
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Walter De Maria Room, permanentInstallation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanentInstallation Context triple: [Walter De Maria Room, permanentInstallation, true]
-
A.
isFixedInstallation
chosen
Indicates that something is permanently installed or affixed in a specific location and not intended to be moved.
-
B.
controlledInstallation
Indicates that an entity has authoritative oversight or management responsibility over the setup, configuration, or deployment of another entity.
-
C.
permanentInfrastructure
Indicates that the relationship involves infrastructure that is intended to be long-lasting, fixed in place, and not temporary or easily removable.
-
D.
permanentPosition
Indicates that an entity holds a long-term, ongoing role or job with another entity, without a predefined end date.
-
E.
permanentAdoption
Indicates a lasting, legally recognized adoption relationship in which the adoptee becomes a permanent member of the adopter’s family.
- 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_69e24585ab1c81909b2b5065d15805d5 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dd47ea48190b32b2a7d37d95654 |
completed | April 29, 2026, 3:41 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:34 p.m.