Triple
T31184261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carthag |
E794991
|
entity |
| Predicate | planetTypeContext |
P62562
|
FINISHED |
| Object | desert 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: desert planet | Statement: [Carthag, planetTypeContext, desert planet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planetTypeContext Context triple: [Carthag, planetTypeContext, desert planet]
-
A.
planetaryBodyContext
Indicates a contextual relationship in which one planetary body is considered or analyzed relative to another body, system, or environment (e.g., its orbital, spatial, or situational setting).
-
B.
hostPlanetType
chosen
Indicates the type or classification of the planet that serves as the host in the relationship.
-
C.
hostStarPlanetType
Indicates that a star serves as the host for a planet of a specified planetary type.
-
D.
planetStatus
Indicates the current condition or classification of a planet, such as its state, category, or operational status within a given context.
-
E.
planetDesignation
Indicates the formal naming or labeling assigned to a planet within a particular cataloging or classification system.
- 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_69f224d675d08190957198068e440422 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:08 p.m.