Triple
T34210982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscount Perth |
E877654
|
entity |
| Predicate | traditionalOrderOfPrecedence |
P6837
|
FINISHED |
| Object | viscount |
—
|
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: viscount | Statement: [Viscount Perth, traditionalOrderOfPrecedence, viscount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalOrderOfPrecedence Context triple: [Viscount Perth, traditionalOrderOfPrecedence, viscount]
-
A.
traditionalPrecedence
Indicates that one entity is accorded higher status, priority, or rank over another according to established tradition or customary order.
-
B.
orderPrecedence
Indicates that one entity must come before another in a defined sequence or priority order.
-
C.
traditionalOrder
chosen
Indicates that entities are arranged or occur according to a customary, historically established sequence or hierarchy.
-
D.
bindingPrecedent
Indicates that a prior decision or ruling must be followed as an authoritative legal standard in deciding a current case.
-
E.
orderOfPrecedenceHigher
Indicates that one entity holds a higher rank or priority than another in an established order of precedence.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
Created at: May 1, 2026, 1:55 a.m.