Triple
T17218422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaled |
E417909
|
entity |
| Predicate | homePlanetStatus |
P66524
|
FINISHED |
| Object | war-ravaged |
—
|
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: war-ravaged | Statement: [Kaled, homePlanetStatus, war-ravaged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homePlanetStatus Context triple: [Kaled, homePlanetStatus, war-ravaged]
-
A.
homePlanet
Indicates the planet that serves as the native or original world of an entity.
-
B.
homeworldStatus
chosen
Indicates the status or condition of an entity’s homeworld in relation to that entity (e.g., origin, current state, or affiliation of the homeworld).
-
C.
homeStatus
Indicates the current condition or state of a home in relation to a specified context (such as occupancy, availability, or operational status).
-
D.
hostPlanet
Indicates that one entity serves as the primary planetary body on which the other entity resides, originates, or is based.
-
E.
hostPlanetType
Indicates the type or classification of the planet that serves as the host in the relationship.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42ddb2b148190b3b50572cc285e3d |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.