Triple
T1549966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish Independent Highland Brigade |
E33066
|
entity |
| Predicate | formedInExile |
P31140
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Polish Independent Highland Brigade, formedInExile, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedInExile Context triple: [Polish Independent Highland Brigade, formedInExile, true]
-
A.
traditionallyExiledTo
Indicates that an entity has, by long-standing custom or tradition, been sent away or banished to a particular place.
-
B.
wasExiled
Indicates that an entity was forcibly sent away from their home or country, typically as a punishment or due to political or social pressures.
-
C.
exiledGovernment
Indicates a government that operates in exile, having been forced to leave and function outside its own country while still claiming authority over it.
-
D.
exiledGovernmentExistence
Indicates that a government continues to exist and operate in exile outside its home territory, typically after losing control of its original state.
-
E.
causeOfExile
Indicates the reason or circumstance that led to an entity’s exile.
- F. None of above. chosen
Provenance (4 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_69a885ee6db8819099502bc5ce8af881 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa574094048190a2d7fc3ac904d51e |
completed | March 6, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69a907b426dc8190975c024a50955368 |
completed | March 5, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_69aa573ee8e0819084abf59f1ddbd1da |
completed | March 6, 2026, 4:25 a.m. |
Created at: March 4, 2026, 7:26 p.m.