Triple
T20114671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sedna |
E490424
|
entity |
| Predicate | isCandidate |
P138743
|
FINISHED |
| Object | dwarf planet |
—
|
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: dwarf planet | Statement: [Sedna, isCandidate, dwarf planet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCandidate Context triple: [Sedna, isCandidate, dwarf planet]
-
A.
wasCandidateIn
Indicates that an entity served as a candidate in a particular election, contest, or selection process.
-
B.
candidateFor
Indicates that one entity is being considered or proposed as a possible choice, option, or selection for another entity (such as a role, position, or outcome).
-
C.
couldElect
Indicates that one entity has the potential or ability, under certain conditions or rules, to choose another entity for an office, role, or position through an election.
-
D.
typicalCandidate
Indicates that an entity is a standard or representative example of what is usually considered a candidate in a given context.
-
E.
allowsCandidacyTo
Indicates that one entity grants another entity the right or eligibility to stand as a candidate for a position, role, or office.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666e3f2288190840d1eb431ac9a1b |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:29 p.m.