Triple
T26464740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Wishing-Chair universe |
E665730
|
entity |
| Predicate | centralObjectFunction |
P170628
|
FINISHED |
| Object | flying chair |
—
|
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: flying chair | Statement: [The Wishing-Chair universe, centralObjectFunction, flying chair]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralObjectFunction Context triple: [The Wishing-Chair universe, centralObjectFunction, flying chair]
-
A.
centralEntity
Indicates that the subject serves as the primary or most important entity around which related entities, actions, or information are organized.
-
B.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
C.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
D.
centralBinaryComponent
Indicates that an entity functions as one of the primary stellar components in a central binary system.
-
E.
centralGoal
Indicates that something is the primary objective or main aim around which other actions, plans, or considerations are organized.
- 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_69ee883e812c8190a9b5a9cdb87fee5e |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f693ffa7908190aa4c451b16df9be6 |
completed | May 3, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 27, 2026, 12:15 a.m.