Triple
T23729507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sutherland |
E586372
|
entity |
| Predicate | hasHistoricClan |
P153733
|
FINISHED |
| Object | Clan Sutherland |
—
|
NE NERFINISHED |
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 Sutherland | Statement: [Sutherland, hasHistoricClan, Clan Sutherland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricClan Context triple: [Sutherland, hasHistoricClan, Clan Sutherland]
-
A.
hasHistoricCommunity
Indicates that an entity is associated with, contains, or is part of a community of historical significance.
-
B.
hasHistoricalPolity
Indicates a relationship where an entity is associated with a political unit or state that existed in the past.
-
C.
hasHistoricity
Indicates that something possesses historical existence, significance, or authenticity, rather than being purely fictional, mythical, or timeless.
-
D.
hasHistoricFranchise
Indicates that an entity is associated with or possesses a franchise that has historical significance or longstanding legacy.
-
E.
hasHistoricalEmpire
Indicates that an entity once possessed, controlled, or was associated with a significant imperial power in the past.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b9180bf48190a6c3656ef0530463 |
completed | April 29, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15b453da88190889a8d9b21727958 |
completed | April 29, 2026, 1:13 a.m. |
Created at: April 17, 2026, 7:09 p.m.