Triple
T37580891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Capitan |
E934953
|
entity |
| Predicate | hasLeadRoleType |
P136950
|
FINISHED |
| Object | heroic swordsman |
—
|
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: heroic swordsman | Statement: [Le Capitan, hasLeadRoleType, heroic swordsman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeadRoleType Context triple: [Le Capitan, hasLeadRoleType, heroic swordsman]
-
A.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
B.
hasPlayingRole
Indicates that an entity participates in an activity, event, or performance in a specific playing role or capacity.
-
C.
replacesInLeadRole
Indicates that one entity takes over or substitutes for another entity in the primary or leading role within a given context or production.
-
D.
leadRoleActor
Indicates that an actor performs a leading or principal role in a work or production.
-
E.
hasHumanCharacterRole
chosen
Indicates that an entity is assigned a role or function specifically associated with a human character within a context such as a story, performance, or representation.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
Created at: May 3, 2026, 4:17 p.m.