Triple
T25938800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tau Ceti b |
E653633
|
entity |
| Predicate | candidateStatus |
P46489
|
FINISHED |
| Object | planet candidate |
—
|
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: planet candidate | Statement: [Tau Ceti b, candidateStatus, planet candidate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: candidateStatus Context triple: [Tau Ceti b, candidateStatus, planet candidate]
-
A.
applicantState
Indicates the current status or condition assigned to an applicant within a process or system.
-
B.
applicantStates
Indicates that an applicant explicitly declares or asserts a particular fact, condition, or piece of information.
-
C.
designationStatus
chosen
Indicates the current official classification or standing assigned to an entity within a defined system or process.
-
D.
associatedWithCandidateStatus
Indicates that there is a relationship linking an entity to a particular status or stage in a candidate-related process.
-
E.
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).
- 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_69e7ab3fd2f881908837305e4ba98011 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6045b07b08190a58fd7e0acda574c |
completed | May 2, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 22, 2026, 8:40 a.m.