Triple
T590932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baroness |
E17267
|
entity |
| Predicate | nobleRankOrder |
P1944
|
FINISHED |
| Object | lowest rank of the British peerage |
—
|
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: lowest rank of the British peerage | Statement: [Baroness, nobleRankOrder, lowest rank of the British peerage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleRankOrder Context triple: [Baroness, nobleRankOrder, lowest rank of the British peerage]
-
A.
nobleRankInScotland
Indicates that an entity holds or is associated with a specific noble rank within the Scottish system of nobility.
-
B.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to another entity.
-
C.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
D.
rankRelativeToPeerage
Indicates how an entity’s hierarchical rank compares to that of a specified peer or peer group within a defined ranking system.
-
E.
rankedAs
chosen
Indicates that one entity is assigned a specific position or level in an ordered ranking relative to others.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bb8ff0081909cd53d88930e2693 |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cc13988190892ca10bd7ae9f09 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.