Triple
T9379897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Floating Heads installation |
E225754
|
entity |
| Predicate | isSuspended |
P88618
|
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: [The Floating Heads installation, isSuspended, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSuspended Context triple: [The Floating Heads installation, isSuspended, true]
-
A.
suspendedIn
Indicates that one entity is held or maintained within another medium or environment without settling or separating.
-
B.
hasSuspension
Indicates that one entity is subject to a temporary suspension imposed or recorded by another entity.
-
C.
suspendedBy
Indicates that one entity has temporarily halted, removed, or placed another entity in an inactive or pending state, typically as an enforcement or administrative action.
-
D.
suspendedFrom
Indicates that one entity is hanging or held up in the air by being attached to another supporting entity.
-
E.
isSuspendedFromRibbon
Indicates that an object is hanging and supported by a ribbon rather than resting on a surface or being directly attached.
- 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_69ca842d8ee88190aaaa639aa953185d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50bc94108190a1b8146a78166009 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89b3368819087a3d69270c1f185 |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:44 p.m.