Triple
T29561816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaminoans |
E750056
|
entity |
| Predicate | roleInCloneWars |
P84139
|
FINISHED |
| Object | manufacturers of clone troopers |
—
|
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: manufacturers of clone troopers | Statement: [Kaminoans, roleInCloneWars, manufacturers of clone troopers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCloneWars Context triple: [Kaminoans, roleInCloneWars, manufacturers of clone troopers]
-
A.
roleDuringCloneWars
chosen
Indicates the specific function, position, or duties an entity held during the time period of the Clone Wars.
-
B.
roleInRogueOne
Indicates that an entity has a specific acting or production role in the film "Rogue One: A Star Wars Story."
-
C.
roleDuringGalacticCivilWar
Indicates the specific function, position, or involvement an entity had during the Galactic Civil War.
-
D.
roleInGalaxy’sEdge
Indicates that an entity has a specific role or function within the context of the Galaxy’s Edge setting or environment.
-
E.
roleOnGalactica
Indicates the specific position, duty, or function an entity holds aboard the Battlestar Galactica.
- 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
Created at: April 28, 2026, 5:20 p.m.