Triple
T23100265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kryptonian |
E576004
|
entity |
| Predicate | planetStatus |
P150917
|
FINISHED |
| Object | destroyed |
—
|
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: destroyed | Statement: [Kryptonian, planetStatus, destroyed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planetStatus Context triple: [Kryptonian, planetStatus, destroyed]
-
A.
exoplanetStatus
Indicates the classification or current condition of a planet located outside our solar system, such as whether it is confirmed, candidate, or unconfirmed as an exoplanet.
-
B.
planetarySystemStatus
Indicates the current condition or operational state of a planetary system, such as its stability, activity level, or lifecycle phase.
-
C.
planetDesignation
Indicates the formal naming or labeling assigned to a planet within a particular cataloging or classification system.
-
D.
habitableZoneStatus
Indicates whether a location or orbit lies within the region around a star where conditions are suitable for liquid water and potentially habitable environments.
-
E.
hasNumberOfConfirmedPlanets
Indicates the relationship that specifies how many planets within a given system or context have been confirmed to exist.
- 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_69e245c060b48190a9bd61a47a16db17 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18de81060819084ab618f05aae583 |
completed | April 29, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69ef89e5ce748190b2c3ac3843484127 |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:58 p.m.