Triple
T14461338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boba Fett |
E358589
|
entity |
| Predicate | takesOverFrom |
P52445
|
FINISHED |
| Object | Jabba the Hutt as crime lord of Tatooine |
—
|
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: Jabba the Hutt as crime lord of Tatooine | Statement: [Boba Fett, takesOverFrom, Jabba the Hutt as crime lord of Tatooine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takesOverFrom Context triple: [Boba Fett, takesOverFrom, Jabba the Hutt as crime lord of Tatooine]
-
A.
takesOver
Indicates that one entity assumes control, ownership, or responsibility for another entity, often replacing its previous controller.
-
B.
tookOverCompetenceFrom
Indicates that one entity assumed responsibility, authority, or functional control previously held by another entity.
-
C.
roleTakenOverFrom
chosen
Indicates that one entity has assumed or inherited a role or position that was previously held by another entity.
-
D.
tookOverLicenseFrom
Indicates that one entity assumed or acquired a license previously held by another entity.
-
E.
tookOverCompanyFrom
Indicates that one entity assumed control or ownership of a company previously controlled or owned by 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91abc1008190a19de4f8f0112c9d |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.