Triple
T32745354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clone Army of the Republic |
E837339
|
entity |
| Predicate | homeworldOfCreation |
P63448
|
FINISHED |
| Object | Kamino |
—
|
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: Kamino | Statement: [Clone Army of the Republic, homeworldOfCreation, Kamino]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeworldOfCreation Context triple: [Clone Army of the Republic, homeworldOfCreation, Kamino]
-
A.
inUniverseBirthplace
Indicates that an entity’s birthplace is located within a specified fictional or defined universe.
-
B.
homeworldType
Indicates the type or classification of a subject’s homeworld (e.g., planet, moon, habitat) in relation to that subject.
-
C.
creatorOfInhabitants
Indicates that an entity is the creator or originator of the beings or inhabitants of another entity (such as a place, world, or domain).
-
D.
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.
-
E.
homeworldLocation
chosen
Indicates the relationship between an entity and the specific place or celestial body that serves as its homeworld.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:12 a.m.