Triple
T37831432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Bowes, 10th Earl of Strathmore and Kinghorne |
E943212
|
entity |
| Predicate | hasTitleOrdinal |
P192434
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [John Bowes, 10th Earl of Strathmore and Kinghorne, hasTitleOrdinal, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleOrdinal Context triple: [John Bowes, 10th Earl of Strathmore and Kinghorne, hasTitleOrdinal, 10]
-
A.
hasOrdinalTitle
chosen
Indicates that an entity holds a title or designation that includes an ordinal position (e.g., first, second, third) within a sequence or hierarchy.
-
B.
hasOrdinaryTitle
Indicates that an entity holds a standard, non-noble or non-honorific title associated with its role or position.
-
C.
hasTitleName
Indicates that an entity possesses or is associated with a specific title or name.
-
D.
hasTitleType
Indicates that an entity holds a specific kind or category of title (such as job title, honorific, or formal designation).
-
E.
hasTitleIn
Indicates that an entity holds or is associated with a specific title within a particular context, domain, or language.
- 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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: May 3, 2026, 4:19 p.m.