Triple
T38368315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Children of the Watch |
E892512
|
entity |
| Predicate | homeworldAssociation |
P63448
|
FINISHED |
| Object | Mandalore |
—
|
NE NERFINISHED |
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: Mandalore | Statement: [Children of the Watch, homeworldAssociation, Mandalore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeworldAssociation Context triple: [Children of the Watch, homeworldAssociation, Mandalore]
-
A.
homeworldType
Indicates the type or classification of a subject’s homeworld (e.g., planet, moon, habitat) in relation to that subject.
-
B.
homeworldStatus
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.
homeworldLocation
chosen
Indicates the relationship between an entity and the specific place or celestial body that serves as its homeworld.
-
D.
homeworldLost
Indicates that an entity has lost its original homeworld, typically through destruction, abandonment, or irreversible separation.
-
E.
adoptedHomeworld
Indicates that an entity has chosen or taken on a particular world as its primary place of residence or affiliation, distinct from its place of origin.
- 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_69f76e47cb4c8190bdd92cd1db59c0c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.