Triple
T4352194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Graham, 1st Marquess of Montrose |
E98051
|
entity |
| Predicate | createdMarquess |
P55713
|
FINISHED |
| Object | 1644 |
—
|
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: 1644 | Statement: [James Graham, 1st Marquess of Montrose, createdMarquess, 1644]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdMarquess Context triple: [James Graham, 1st Marquess of Montrose, createdMarquess, 1644]
-
A.
createdBaronOrBaronessOf
Indicates that one entity granted or established the noble title of baron or baroness for another entity.
-
B.
createdBaronet
Indicates that one entity formally established or granted a baronetcy title to another entity.
-
C.
succeededByInMarquessate
Indicates that one entity was the immediate successor of another in holding a particular marquessate title.
-
D.
createdDukeOfClarence
Indicates the relationship in which one entity formally granted or established the noble title "Duke of Clarence" for another entity.
-
E.
hasNotableMarquessate
Indicates that an entity holds or is associated with a marquessate that is considered historically or socially notable.
- 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351ab03488190a8900de98fb4a00e |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff654308190b9717526120d80d3 |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:15 p.m.