Triple
T26943045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Captain Rex |
E678568
|
entity |
| Predicate | closePartnerOf |
P33497
|
FINISHED |
| Object | Anakin Skywalker |
—
|
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: Anakin Skywalker | Statement: [Captain Rex, closePartnerOf, Anakin Skywalker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closePartnerOf Context triple: [Captain Rex, closePartnerOf, Anakin Skywalker]
-
A.
cooperationPartner
Indicates that two entities are engaged in a collaborative relationship, working together toward shared goals or mutual benefit.
-
B.
operatesInClosePartnershipWith
chosen
Indicates a collaborative relationship in which two entities work together closely and continuously, coordinating their activities and decisions as near-partners.
-
C.
partnerInOrganizationWith
Indicates that two entities are associated as partners within the same organization or organizational context.
-
D.
partnerInActWith
Indicates that two or more entities jointly participate as partners in carrying out the same act or action.
-
E.
partnerInWorkOf
Indicates a collaborative relationship where one entity works together with another on a shared task, project, or professional activity.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 6:19 a.m.