Triple
T29561935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaminoan cloners |
E750059
|
entity |
| Predicate | employedTemplate |
P83995
|
FINISHED |
| Object | Jango Fett |
—
|
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: Jango Fett | Statement: [Kaminoan cloners, employedTemplate, Jango Fett]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employedTemplate Context triple: [Kaminoan cloners, employedTemplate, Jango Fett]
-
A.
employedPeople
Indicates that there exists a relationship where people are currently working in jobs or positions, typically under an employer.
-
B.
employedThrough
Indicates that an entity holds a job or work position by means of, or via the arrangement of, another entity (such as an agency, contractor, or intermediary).
-
C.
employedSystem
Indicates that a system is used or operated in the context of an employment or work-related arrangement.
-
D.
employedMethod
Indicates that a particular method, technique, or procedure was used to carry out an action or achieve a result.
-
E.
employedTo
chosen
Indicates that one entity is hired or engaged to perform work, services, or duties for another entity.
- 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_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 28, 2026, 5:20 p.m.