Triple
T22716841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Counter-Earth |
E561755
|
entity |
| Predicate | hasNoEmpiricalEvidence |
P52085
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Counter-Earth, hasNoEmpiricalEvidence, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoEmpiricalEvidence Context triple: [Counter-Earth, hasNoEmpiricalEvidence, true]
-
A.
hasNoEvidenceOf
chosen
Indicates that there is no supporting proof, data, or documentation confirming the existence or occurrence of the referenced condition, event, or relationship.
-
B.
hasMaterialEvidence
Indicates that there exists tangible, physical evidence supporting or associated with a particular entity, event, or claim.
-
C.
hasEvidentials
Indicates that a statement, claim, or information is accompanied by markers specifying the type or source of evidence supporting it.
-
D.
hasEconomicEvidence
Indicates that there exists supporting economic data, analysis, or documentation demonstrating or justifying the referenced relationship or claim.
-
E.
providesEvidenceFor
Indicates that one entity serves as support, justification, or proof for the validity or truth 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1790e14c88190af6acb27910ae9c1 |
completed | April 29, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:19 p.m.