Triple
T12755753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Euston |
E304854
|
entity |
| Predicate | peerageStatus |
P86178
|
FINISHED |
| Object | courtesy |
—
|
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: courtesy | Statement: [Earl of Euston, peerageStatus, courtesy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peerageStatus Context triple: [Earl of Euston, peerageStatus, courtesy]
-
A.
peerageSystem
Indicates a hierarchical system of noble ranks and titles that defines relative status and privileges among members of a nobility.
-
B.
typeOfPeerage
Indicates the specific rank or category within a system of peerage that a given title or noble status belongs to.
-
C.
peerageForLife
Indicates that an individual holds a noble title or rank granted for the duration of their lifetime only, without hereditary succession.
-
D.
peerageCreated
Indicates that a noble title or rank within a peerage system has been formally established or conferred.
-
E.
aristocraticTitleStatus
chosen
Indicates the status or condition of an entity’s aristocratic or noble title (e.g., whether and how the title is held, recognized, or used).
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8b57b88190b29b8fdca415c81c |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:27 p.m.