Triple
T11025598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clan MacLeod |
E260607
|
entity |
| Predicate | governingSystemHistorically |
P49184
|
FINISHED |
| Object | Clan system |
—
|
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: Clan system | Statement: [Clan MacLeod, governingSystemHistorically, Clan system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingSystemHistorically Context triple: [Clan MacLeod, governingSystemHistorically, Clan system]
-
A.
politicalSystemHistorical
Indicates a relationship where a political system is characterized or analyzed in terms of its historical development, context, or evolution.
-
B.
hasHistoricalGovernmentForm
chosen
Indicates that an entity has, at some point in the past, been governed under a particular form or system of government.
-
C.
historicalRegime
Indicates that one entity functioned as a governing regime or ruling authority over another entity during a specific historical period.
-
D.
governedByInPast
Indicates that an entity was under the rule, control, or authority of another entity during a previous time period.
-
E.
hasHistoricalPolity
Indicates a relationship where an entity is associated with a political unit or state that existed 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797d0cd988190a7b21d7bdc3109ce |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d7440087ac8190aef2e6f6b13b2635 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:25 p.m.