Triple
T16739782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British order of precedence |
E406805
|
entity |
| Predicate | secondRankHeldBy |
P97688
|
FINISHED |
| Object | consort of the sovereign |
—
|
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: consort of the sovereign | Statement: [British order of precedence, secondRankHeldBy, consort of the sovereign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondRankHeldBy Context triple: [British order of precedence, secondRankHeldBy, consort of the sovereign]
-
A.
officeHolderRankSometimes
Indicates that an office holder’s rank or level within a position can vary or apply only in certain situations or periods.
-
B.
rankHeldByOfficeholder
Indicates the specific rank or level associated with an office or position that is held by a particular officeholder.
-
C.
secondSupremeLeader
Indicates that the subject is the second individual to hold the position of supreme leader of the object entity.
-
D.
secondRank
chosen
Indicates that one entity holds the second position or rank in order or hierarchy relative to others.
-
E.
rankHeldByPost
Indicates that a particular organizational post or position is associated with, or carries, a specific rank.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c3d4fa48190b0db8f10a39d3ad8 |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.