Triple
T28586008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Consort |
E723505
|
entity |
| Predicate | grantsStyle |
P1607
|
FINISHED |
| Object | royal highness in many monarchies |
—
|
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: royal highness in many monarchies | Statement: [Princess Consort, grantsStyle, royal highness in many monarchies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantsStyle Context triple: [Princess Consort, grantsStyle, royal highness in many monarchies]
-
A.
styleGranted
chosen
Indicates that a particular style, manner, or mode of expression has been conferred or authorized for use by one entity to another.
-
B.
grantsAre
Indicates that one entity provides or awards grants to another entity.
-
C.
patronageStyle
Indicates the manner or characteristic way in which support, sponsorship, or patronage is provided in a relationship.
-
D.
governsInStyle
Indicates that a governing entity exercises authority or leadership in a distinctive, notable, or characteristic manner.
-
E.
grantedHonor
Indicates that one entity has formally bestowed an honor, award, or distinction upon another entity.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 28, 2026, 4:17 a.m.