Triple
T8832871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaise cassée |
E210186
|
entity |
| Predicate | temporaryRemoval |
P31792
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [Chaise cassée, temporaryRemoval, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporaryRemoval Context triple: [Chaise cassée, temporaryRemoval, 2005]
-
A.
temporarilyAbolished
Indicates that a rule, institution, practice, or status has been officially suspended or done away with for a limited period of time rather than permanently.
-
B.
removalPeriod
chosen
Indicates the time span during which something is taken away, deleted, or otherwise removed from availability or consideration.
-
C.
temporaryLocation
Indicates that an entity is located at a place for a limited or non-permanent duration.
-
D.
temporarilyRestored
Indicates that a previously unavailable or altered state, condition, or connection has been brought back to its former status for a limited or non-permanent period.
-
E.
temporaryClosure
Indicates that an entity is closed or unavailable for a limited, non-permanent period of time.
- 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_69ca8388549c819095fd94eadefbb007 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc605005788190a4df1fe317f3056a |
completed | April 1, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:47 p.m.