Triple
T35077687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birkebeiner faction |
E1012347
|
entity |
| Predicate | statusAfterVictory |
P109227
|
FINISHED |
| Object | became ruling royal party in Norway |
—
|
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: became ruling royal party in Norway | Statement: [Birkebeiner faction, statusAfterVictory, became ruling royal party in Norway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterVictory Context triple: [Birkebeiner faction, statusAfterVictory, became ruling royal party in Norway]
-
A.
statusAfterBattle
chosen
Indicates the condition or state of an entity following the completion of a battle or combat encounter.
-
B.
victoryIn
Indicates that one entity achieves a win or success in a specific contest, event, or competitive context involving another entity.
-
C.
grantedVictoryBy
Indicates that one entity is awarded or credited with a victory by another entity.
-
D.
typeOfVictory
Indicates the specific manner or category in which a victory was achieved.
-
E.
conditionOfVictory
Indicates the specific circumstances or criteria under which a participant is considered to have won.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff7bc112088190851501fb2a16103d |
completed | May 9, 2026, 6:24 p.m. |
| PD | Predicate disambiguation | batch_69ff7b45507c81909753866ad733601a |
completed | May 9, 2026, 6:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.