Triple
T22977504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnick Odair |
E571365
|
entity |
| Predicate | roleInRebellion |
P88009
|
FINISHED |
| Object | key rebel figure |
—
|
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: key rebel figure | Statement: [Finnick Odair, roleInRebellion, key rebel figure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInRebellion Context triple: [Finnick Odair, roleInRebellion, key rebel figure]
-
A.
roleInRevolt
chosen
Indicates the specific function, position, or level of participation an entity had within a particular revolt or uprising.
-
B.
typeOfRebel
Indicates that one entity is a rebel belonging to, or classified under, a particular type or category of rebellion.
-
C.
roleInMutiny
Indicates that one entity participated in a mutiny with a specific role or capacity in that rebellious action.
-
D.
associatedWithRebelGroup
Indicates that one entity is connected or linked in some capacity to a rebel group, such as through membership, support, collaboration, or affiliation.
-
E.
roleInLibyanCivilWar
Indicates the specific involvement, function, or position an entity had in the context of the Libyan Civil War.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18292f3788190ab4e9d559e0070c8 |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:48 p.m.