Triple
T7272893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tau Ceti f |
E161147
|
entity |
| Predicate | existenceCertainty |
P9983
|
FINISHED |
| Object | contested |
—
|
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: contested | Statement: [Tau Ceti f, existenceCertainty, contested]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existenceCertainty Context triple: [Tau Ceti f, existenceCertainty, contested]
-
A.
hasCertainty
Indicates that a statement, belief, or relationship is associated with a specific level or degree of confidence or surety.
-
B.
uncertainty
chosen
Indicates that there is doubt, lack of sureness, or incomplete confidence about a fact, outcome, or state of affairs in the relationship or situation described.
-
C.
narrativeCertainty
Indicates the degree of confidence or definitiveness with which a narrative, statement, or account is presented as true or reliable.
-
D.
hasUncertainty
Indicates that the relationship or value is associated with some level or type of uncertainty rather than being fully definite or precise.
-
E.
confirmationPower
Indicates that one entity has the authority or capacity to approve, validate, or formally confirm the actions, decisions, or status of another entity.
- 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_69c6885181008190b419040e22939c7c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:58 p.m.