Triple
T29953067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broken Chair |
E760817
|
entity |
| Predicate | returnedToSite |
P45021
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Broken Chair, returnedToSite, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedToSite Context triple: [Broken Chair, returnedToSite, 2007]
-
A.
returnedFrom
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
-
B.
returnedToTour
Indicates that an entity resumed or went back to participating in a tour after having left or paused it.
-
C.
returnedVia
Indicates that something was sent back or responded to through a specified medium, channel, or method.
-
D.
returnedToOrganization
Indicates that an entity went back to or rejoined a specific organization after having left or been away.
-
E.
returnsTo
chosen
Indicates that an entity goes back to a previous location, state, or entity it was associated with before.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 29, 2026, 6:26 p.m.