Triple
T26211345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tau Ceti c |
E655497
|
entity |
| Predicate | detectionStatus |
P26043
|
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 c, detectionStatus, planet candidate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detectionStatus Context triple: [Tau Ceti c, detectionStatus, planet candidate]
-
A.
detected
Indicates that an entity has observed, identified, or discovered the presence or occurrence of another entity or event.
-
B.
hasModeOfDetection
Indicates that one entity is identified, measured, or observed using a specified method or technique of detection.
-
C.
recognitionStatus
Indicates the current state or outcome of acknowledging, validating, or officially accepting something or someone.
-
D.
hasDiscoveryStatus
chosen
Indicates the current state or phase of discovery or identification associated with an entity.
-
E.
seeStatus
Indicates that one entity observes or becomes aware of the current state or condition of another entity or process.
- 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_69ee5b49adb4819086545280d4ef6337 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60d1706d481908ca3c7c39ba0d157 |
completed | May 2, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:52 p.m.