Triple
T29544666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Below Princess of the Blood Royal |
E749598
|
entity |
| Predicate | typeOfPrecedence |
P69114
|
FINISHED |
| Object | social precedence |
—
|
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: social precedence | Statement: [Below Princess of the Blood Royal, typeOfPrecedence, social precedence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPrecedence Context triple: [Below Princess of the Blood Royal, typeOfPrecedence, social precedence]
-
A.
orderPrecedence
Indicates that one entity must come before another in a defined sequence or priority order.
-
B.
bindingPrecedent
Indicates that a prior decision or ruling must be followed as an authoritative legal standard in deciding a current case.
-
C.
orderOfPrecedenceGroup
chosen
Indicates the hierarchical ranking or priority grouping of entities relative to one another.
-
D.
orderOfPrecedenceHigher
Indicates that one entity holds a higher rank or priority than another in an established order of precedence.
-
E.
confersPrecedenceIn
Indicates that one entity is granted higher priority, rank, or standing over another within a specified context or domain.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
Created at: April 28, 2026, 5:06 p.m.