Triple
T27267771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount Boyle |
E687952
|
entity |
| Predicate | socialHierarchyRank |
P80950
|
FINISHED |
| Object | rank below earl and above baron |
—
|
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: rank below earl and above baron | Statement: [Viscount Boyle, socialHierarchyRank, rank below earl and above baron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialHierarchyRank Context triple: [Viscount Boyle, socialHierarchyRank, rank below earl and above baron]
-
A.
socialHierarchy
Indicates a relationship where entities are ordered or ranked by social status, power, or authority relative to one another.
-
B.
partyHierarchyRank
Indicates the relative position or level of an entity within an ordered party hierarchy.
-
C.
legalHierarchyRank
Indicates the relative position or level of authority an entity holds within a legal or judicial hierarchy.
-
D.
nobleRankInHierarchy
chosen
Indicates the relative position or level of a noble title within a structured hierarchy of ranks.
-
E.
heightRankWithinStructure
Indicates the relative ordering of an entity’s height compared to other entities within the same structure.
- 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_69ef3557abc481908bf3c146f0f3356a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 10:57 a.m.