Triple
T25745544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | inner Solar System |
E648335
|
entity |
| Predicate | containsPlanetType |
P176258
|
FINISHED |
| Object | terrestrial planet |
—
|
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: terrestrial planet | Statement: [inner Solar System, containsPlanetType, terrestrial planet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPlanetType Context triple: [inner Solar System, containsPlanetType, terrestrial planet]
-
A.
hasCentralPlanetType
Indicates that an entity has a central planet whose type or classification is specified by the related value.
-
B.
hasPlanetaryFeatureType
Indicates that an entity possesses or is associated with a specific type of planetary surface or geological feature.
-
C.
hasPlanet
Indicates that one entity possesses, contains, or is associated with a particular planet as part of its system or domain.
-
D.
isPlanet
Indicates that the subject entity is classified as a planet.
-
E.
hostPlanetType
Indicates the type or classification of the planet that serves as the host in the relationship.
- F. None of above. chosen
Provenance (4 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6dfcafd0c81908d86662948c539d6 |
completed | May 3, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6df418f488190a5e7ff41f32dceda |
completed | May 3, 2026, 5:38 a.m. |
Created at: April 22, 2026, 3:51 a.m.