Triple
T25450731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess-Mother of the Netherlands |
E637772
|
entity |
| Predicate | royalContext |
P26514
|
FINISHED |
| Object | House of Orange-Nassau |
—
|
NE NERFINISHED |
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: House of Orange-Nassau | Statement: [Princess-Mother of the Netherlands, royalContext, House of Orange-Nassau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalContext Context triple: [Princess-Mother of the Netherlands, royalContext, House of Orange-Nassau]
-
A.
royalUse
Indicates that something is used, employed, or reserved specifically by or for a royal person or royal institution.
-
B.
royalFunction
Indicates a role, duty, or activity specifically associated with royalty or the exercise of royal authority.
-
C.
monarchicContext
chosen
Indicates that the relationship or action occurs within, is shaped by, or pertains to a monarchical system of rule or authority.
-
D.
royalStyle
Indicates the formal manner or title by which a monarch or royal person is officially addressed or referred to.
-
E.
royalAppointment
Indicates a formal position, role, or honor that has been officially granted to an entity by a monarch or royal authority.
- 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f707066c8190af40ac74d91a20c9 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:03 p.m.