Triple
T34681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Equator |
E689
|
entity |
| Predicate | planetaryAnalogue |
P1868
|
FINISHED |
| Object | other planets also have equators |
—
|
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: other planets also have equators | Statement: [Equator, planetaryAnalogue, other planets also have equators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planetaryAnalogue Context triple: [Equator, planetaryAnalogue, other planets also have equators]
-
A.
wasColonyOf
Indicates that one entity functioned as a colony under the political control or administration of another entity.
-
B.
spaceProgram
Indicates that an entity is involved in, operates, or is associated with an organized program dedicated to space exploration, research, or related activities.
-
C.
envisionedAs
Indicates that one entity is mentally pictured, imagined, or conceived in terms of another entity or role.
-
D.
parallels
chosen
Indicates that one entity runs alongside or corresponds to another in a way that maintains a consistent separation or similarity without intersecting.
-
E.
hasLandform
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a2490019948190a89bb0910c60d462 |
completed | Feb. 28, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69a24872e4e481908567850168d65015 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.