Triple
T25295251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marquess of Lorne |
E634198
|
entity |
| Predicate | titleHolderAlsoStyledAs |
P17682
|
FINISHED |
| Object | Lord Lorne |
—
|
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: Lord Lorne | Statement: [Marquess of Lorne, titleHolderAlsoStyledAs, Lord Lorne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderAlsoStyledAs Context triple: [Marquess of Lorne, titleHolderAlsoStyledAs, Lord Lorne]
-
A.
titleHolderStyle
chosen
Indicates the manner or format in which a title holder’s status or designation is presented or styled in relation to another entity.
-
B.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
C.
titleHolderIsUsually
Indicates that an entity serving as a title holder is typically or most commonly a particular type or category of entity.
-
D.
titleHolderUnder
Indicates that one entity holds a title, position, or rank under the authority, jurisdiction, or hierarchy of another entity.
-
E.
titleHolderWas
Indicates that an entity previously held a specific title or position before it passed to someone or something else.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 21, 2026, 1:22 p.m.