Triple
T14090031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan MacLachlan |
E339102
|
entity |
| Predicate | hasHistoricAllegiance |
P53264
|
FINISHED |
| Object | Jacobite cause |
—
|
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: Jacobite cause | Statement: [Clan MacLachlan, hasHistoricAllegiance, Jacobite cause]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricAllegiance Context triple: [Clan MacLachlan, hasHistoricAllegiance, Jacobite cause]
-
A.
hadAllegiance
chosen
Indicates that an entity was loyally committed or formally bound in support or service to another entity, such as a person, group, or cause.
-
B.
hasHistoricalPolity
Indicates a relationship where an entity is associated with a political unit or state that existed in the past.
-
C.
hasHistoricTerritory
Indicates that an entity possesses or claims a territory that it historically occupied, controlled, or was associated with in the past.
-
D.
hasHistoricalEmpire
Indicates that an entity once possessed, controlled, or was associated with a significant imperial power in the past.
-
E.
historicallyBorneBy
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5ee3213c8190af2853a2a5b302a2 |
completed | April 14, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69de05b0e6c88190a819eeba0028981f |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.