Triple
T26238993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Montrose |
E656255
|
entity |
| Predicate | notableHolderLoyalty |
P197119
|
FINISHED |
| Object | Charles I of England |
—
|
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: Charles I of England | Statement: [Earl of Montrose, notableHolderLoyalty, Charles I of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHolderLoyalty Context triple: [Earl of Montrose, notableHolderLoyalty, Charles I of England]
-
A.
notableHolder
Indicates that a person or entity is a distinguished or prominent holder of a particular position, title, or role.
-
B.
hasLoyalties
Indicates that an entity feels allegiance or commitment toward one or more other entities or causes.
-
C.
loyaltySymbolizedBy
Indicates that an instance of loyalty is represented or expressed by a particular symbol or emblem.
-
D.
isLoyalTo
Indicates that one entity consistently supports, respects, or remains faithful to another entity.
-
E.
notableHolderDescription
Indicates a descriptive statement about a person or entity that is notably associated with holding a particular position, title, or role.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
| PDg | Predicate description generation | batch_69fe78e35e6c8190b8b440777912f64e |
completed | May 8, 2026, 11:59 p.m. |
Created at: April 26, 2026, 9:03 p.m.