Triple
T35682802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Argyll |
E1031055
|
entity |
| Predicate | titleHolderCharacteristic |
P200438
|
FINISHED |
| Object | powerful regional ruler |
—
|
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: powerful regional ruler | Statement: [Lord of Argyll, titleHolderCharacteristic, powerful regional ruler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderCharacteristic Context triple: [Lord of Argyll, titleHolderCharacteristic, powerful regional ruler]
-
A.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
B.
titleHolderName
Indicates the name of the person or entity that holds a particular title or position.
-
C.
titleHolderType
Indicates the specific role or capacity in which an entity holds a title (e.g., owner, trustee, beneficiary).
-
D.
titleHolderIsUsually
Indicates that an entity serving as a title holder is typically or most commonly a particular type or category of entity.
-
E.
titleHolderSee
Indicates that one who holds a title or position observes, meets, or has an in-person encounter with another entity.
- 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_69f76e0bb6608190ad3a1880be54a17d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff8aff48988190a48a440de8238ef9 |
completed | May 9, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69ff8a780404819082f48ceb21e7fe11 |
completed | May 9, 2026, 7:26 p.m. |
| PDg | Predicate description generation | batch_69ff8afe9d5c8190bd5ae434fc2b550b |
completed | May 9, 2026, 7:29 p.m. |
Created at: May 3, 2026, 4:05 p.m.