Triple
T2736852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Townshend, 1st Viscount Sydney |
E60649
|
entity |
| Predicate | ordinalOfNobleTitle |
P18767
|
FINISHED |
| Object | 1st |
—
|
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: 1st | Statement: [Thomas Townshend, 1st Viscount Sydney, ordinalOfNobleTitle, 1st]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordinalOfNobleTitle Context triple: [Thomas Townshend, 1st Viscount Sydney, ordinalOfNobleTitle, 1st]
-
A.
nobleTitleNumber
chosen
Indicates the ordinal number or sequence position associated with a person's noble title (e.g., first duke, second baron).
-
B.
rankInBritishPeerageSystem
Indicates the specific noble title or level an entity holds within the hierarchical structure of the British peerage system.
-
C.
rankRelativeToPeerage
Indicates how an entity’s hierarchical rank compares to that of a specified peer or peer group within a defined ranking system.
-
D.
associatedNobleTitle
Indicates that an entity is linked to or bears a particular noble or aristocratic title.
-
E.
isRoyalTitle
Indicates that something is a formal title associated with royalty or a royal rank.
- 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_69ab4b77febc819095603eb012cd141b |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb11c66c81909058f2978aa5fae9 |
completed | March 7, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69abd82859348190bce3be8f2e9d60ba |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.