Triple
T14683180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Arrows Division |
E344838
|
entity |
| Predicate | ideologySide |
P496
|
FINISHED |
| Object | Nationalist |
—
|
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: Nationalist | Statement: [Blue Arrows Division, ideologySide, Nationalist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ideologySide Context triple: [Blue Arrows Division, ideologySide, Nationalist]
-
A.
politicalSide
Indicates the political alignment or ideological position that one entity holds in relation to political spectra or groupings.
-
B.
opposingFactionIdeology
Indicates that two factions hold ideologies that are in direct conflict or fundamental opposition to each other.
-
C.
ideology
chosen
Indicates the belief system or set of political, social, or philosophical principles that an entity adheres to or promotes.
-
D.
ideologicalRange
Indicates the span or spectrum of ideological positions or beliefs associated with an entity, typically from one end of a defined ideological scale to the other.
-
E.
opposingIdeology
Indicates that two entities hold conflicting or mutually incompatible belief systems, doctrines, or ideological positions.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb56a51ec8190941684fd562a7182 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.