Triple
T5733248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Lorne |
E126435
|
entity |
| Predicate | notASeparatePeerage |
P50880
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lord Lorne, notASeparatePeerage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notASeparatePeerage Context triple: [Lord Lorne, notASeparatePeerage, true]
-
A.
isNotPeerage
chosen
Indicates that the entity does not belong to any recognized peerage or noble rank within a hierarchical social or nobility system.
-
B.
peerageRankBelow
Indicates that one entity holds a lower rank or status in a peerage or nobility hierarchy than another entity.
-
C.
hasNotableDukedom
Indicates that an entity holds or is associated with a dukedom that is considered historically or culturally significant.
-
D.
hasNotableMarquessate
Indicates that an entity holds or is associated with a marquessate that is considered historically or socially notable.
-
E.
typeOfPeerage
Indicates the specific rank or category within a system of peerage that a given title or noble status belongs to.
- 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_69c0083082288190b7478cead6b5430a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c6488881909bed4a4534d57f70 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:47 p.m.