Triple
T18583680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navarrese Civil War |
E454183
|
entity |
| Predicate | hasBelligerentFaction |
P53524
|
FINISHED |
| Object | Beamontese faction |
—
|
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: Beamontese faction | Statement: [Navarrese Civil War, hasBelligerentFaction, Beamontese faction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBelligerentFaction Context triple: [Navarrese Civil War, hasBelligerentFaction, Beamontese faction]
-
A.
hasOpposingFaction
chosen
Indicates that one faction stands in opposition or conflict to another faction.
-
B.
hasFaction
Indicates that an entity is affiliated with, belongs to, or is represented by a particular faction or group.
-
C.
belligerentFor
Indicates a relationship in which one entity is engaged in hostile or aggressive behavior toward, or in conflict with, another entity.
-
D.
hasMajorFaction
Indicates that an entity possesses or is associated with a primary or dominant faction within a given context.
-
E.
foughtForFaction
Indicates that an entity actively participated in or supported a particular faction, typically in a conflict or struggle.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e543d200dc8190b8797d731f4e4865 |
completed | April 19, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.