Triple
T30075271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European peerage ranks |
E764300
|
entity |
| Predicate | hasIntermediateRank |
P182514
|
FINISHED |
| Object | marquess |
—
|
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: marquess | Statement: [European peerage ranks, hasIntermediateRank, marquess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIntermediateRank Context triple: [European peerage ranks, hasIntermediateRank, marquess]
-
A.
isMidLevelRank
chosen
Indicates that an entity holds a rank or position that is in the middle tier of a defined hierarchy, between lower and higher levels.
-
B.
hasIntermediate
Indicates that there exists one or more entities that serve as a middle or transitional step between two related entities or stages.
-
C.
containsRank
Indicates that one entity includes or encompasses another entity that has a specific rank or hierarchical level within it.
-
D.
isRanked
Indicates that an entity has been assigned a position or level within an ordered hierarchy or comparative list.
-
E.
hasSubranking
Indicates that one ranking is a subordinate or nested ranking within another ranking.
- 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_69f22472eee081909791dc372aa766e9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fec4cffed08190b5e5e7cc0c87493e |
completed | May 9, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_69fec2ea7fe08190bd751b39515f69d1 |
completed | May 9, 2026, 5:15 a.m. |
Created at: April 29, 2026, 7:01 p.m.