Triple
T18954599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhein II |
E463737
|
entity |
| Predicate | removesFromOriginalScene |
P89276
|
FINISHED |
| Object | buildings |
—
|
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: buildings | Statement: [Rhein II, removesFromOriginalScene, buildings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removesFromOriginalScene Context triple: [Rhein II, removesFromOriginalScene, buildings]
-
A.
retainsSceneGraph
Indicates that an operation or transformation preserves the original structure and relationships of the scene graph without discarding or fundamentally altering it.
-
B.
recreatesScene
Indicates that one entity reproduces or stages a scene or event depicted, described, or occurring in another entity.
-
C.
laterRemovedTo
Indicates that an entity was moved or transferred to a location or state at a later time, after an earlier condition or placement.
-
D.
removedElementFromPredecessor
chosen
Indicates that an element has been taken out or deleted from an immediately preceding entity in a sequence or structure.
-
E.
removedBefore
Indicates that one entity was removed or taken away earlier in time than another specified entity or 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d546babc81909d4fc5b6b4441aac |
completed | April 20, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon