Triple
T4361535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Corsaire |
E98672
|
entity |
| Predicate | hasCharacterRoleType |
P49696
|
FINISHED |
| Object | pirate |
—
|
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: pirate | Statement: [Le Corsaire, hasCharacterRoleType, pirate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharacterRoleType Context triple: [Le Corsaire, hasCharacterRoleType, pirate]
-
A.
actingRoleType
Indicates the specific type or category of role an entity performs when acting in a particular capacity or function.
-
B.
workCharacterType
chosen
Indicates that a work involves or features a character of a specified type or role.
-
C.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
D.
featuresCharacterRole
Indicates that a work includes a character appearing in a specific narrative or functional role.
-
E.
actorRole
Indicates that an entity participates in an event or action in a specific capacity or function (such as performer, initiator, or responsible party).
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351e47d388190b31500189577cd75 |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:16 p.m.