Triple
T6208575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess of Norway |
E138808
|
entity |
| Predicate | hasProtocolRank |
P34969
|
FINISHED |
| Object | high-ranking member of royal family |
—
|
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: high-ranking member of royal family | Statement: [Princess of Norway, hasProtocolRank, high-ranking member of royal family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtocolRank Context triple: [Princess of Norway, hasProtocolRank, high-ranking member of royal family]
-
A.
rankInProtocol
chosen
Indicates the relative position or precedence an entity holds within an ordered protocol or formal hierarchy.
-
B.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
C.
hasFlagProtocol
Indicates that an entity is associated with, governed by, or operates under a specific flag protocol or set of flag-related rules.
-
D.
hasProtocolStatus
Indicates that an entity is associated with a particular protocol-related state or condition it currently holds.
-
E.
hasRankOrder
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
- 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_69c008ada364819096c9e92c74d639b5 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062870d5881909b8d4e33ff31a907 |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:21 p.m.