Triple
T29754233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Dutton |
E752985
|
entity |
| Predicate | titleHierarchyLevel |
P35573
|
FINISHED |
| Object | below an earl |
—
|
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: below an earl | Statement: [Baron Dutton, titleHierarchyLevel, below an earl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHierarchyLevel Context triple: [Baron Dutton, titleHierarchyLevel, below an earl]
-
A.
titleHierarchy
chosen
Indicates a hierarchical relationship between titles, where one title is ranked above or below another in an ordered structure.
-
B.
ringHierarchyLevel
Indicates the position or rank of an entity within a structured ring-based hierarchy.
-
C.
hierarchyLevelCode
Indicates the specific rank or position an entity holds within a defined hierarchy or organizational structure.
-
D.
designationLevel
Indicates the specific rank, tier, or level assigned to an entity within a designation or classification system.
-
E.
levelInAdministrativeHierarchy
Indicates the relative position or rank of an administrative unit within a broader hierarchical administrative 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: April 28, 2026, 7:55 p.m.