Triple
T38353351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Middlesex |
E1046255
|
entity |
| Predicate | positionInFeudalHierarchy |
P80950
|
FINISHED |
| Object | high nobility |
—
|
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: high nobility | Statement: [Earl of Middlesex, positionInFeudalHierarchy, high nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInFeudalHierarchy Context triple: [Earl of Middlesex, positionInFeudalHierarchy, high nobility]
-
A.
feudalStatus
Indicates the hierarchical social or legal position an entity holds within a feudal system, such as lord, vassal, or serf.
-
B.
positionOnNobility
Indicates the rank or status an entity holds within a hierarchy of nobility.
-
C.
positionInCasteSystem
Indicates the relative social rank or standing an entity holds within a hierarchical caste system.
-
D.
nobleRankInHierarchy
chosen
Indicates the relative position or level of a noble title within a structured hierarchy of ranks.
-
E.
feudalFunction
Indicates the role or duty an entity holds within a feudal hierarchy, such as obligations, services, or functions owed to or performed for another.
- 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_69f76e3a94fc81908edc175e8d259e80 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a002ae74da08190a4b47e0ff0f7f8fe |
completed | May 10, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_6a0029cc369c81909578e52c4a75ab18 |
completed | May 10, 2026, 6:46 a.m. |
Created at: May 3, 2026, 4:31 p.m.