Triple
T19663064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulster British |
E472132
|
entity |
| Predicate | nationalAllegiance |
P32110
|
FINISHED |
| Object | British |
—
|
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: British | Statement: [Ulster British, nationalAllegiance, British]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalAllegiance Context triple: [Ulster British, nationalAllegiance, British]
-
A.
nationalAlignment
Indicates how closely an entity’s interests, policies, or actions are aligned with those of a particular nation or national government.
-
B.
countryOfAllegiance
chosen
Indicates the country to which an entity owes loyalty, support, or official allegiance.
-
C.
allegiance
Indicates a relationship where one entity is loyal, committed, or obligated in support or service to another entity.
-
D.
stateAllegiance
Indicates that one entity formally declares loyalty or support to another entity, such as a person, group, or state.
-
E.
nationalAffiliation
Indicates a relationship where an entity is officially associated with, belongs to, or is identified as part of a particular nation or country.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6416671fc81908e25b0477234fa0f |
completed | April 20, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.