Triple
T7272848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tau Ceti e |
E161146
|
entity |
| Predicate | systemPlanetCount |
P50044
|
FINISHED |
| Object | at least four candidate planets |
—
|
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: at least four candidate planets | Statement: [Tau Ceti e, systemPlanetCount, at least four candidate planets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: systemPlanetCount Context triple: [Tau Ceti e, systemPlanetCount, at least four candidate planets]
-
A.
planetaryCountConsidered
chosen
Indicates that a specific number of planets is taken into account or evaluated within a given context or analysis.
-
B.
numberOfStarsWithPlanets
Indicates the count of stars that have one or more planets associated with them.
-
C.
majorBody
Indicates that one entity is the primary or most significant body (e.g., celestial, organizational, or governing body) in relation to another entity.
-
D.
hasNumberOfKnownMoons
Indicates the relationship that specifies how many moons are known to orbit a given celestial body.
-
E.
cosmicBodies
Indicates a relationship in which entities are identified as astronomical or celestial objects existing in outer space.
- 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.