Triple
T27478803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | throne of Belgium |
E693540
|
entity |
| Predicate | hasHereditaryRoleFor |
P88266
|
FINISHED |
| Object | Belgian royal family |
—
|
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: Belgian royal family | Statement: [throne of Belgium, hasHereditaryRoleFor, Belgian royal family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHereditaryRoleFor Context triple: [throne of Belgium, hasHereditaryRoleFor, Belgian royal family]
-
A.
hasConservedRoleIn
Indicates that an entity maintains the same or a similar functional role across different contexts, conditions, or evolutionary lineages.
-
B.
hasRelativeRole
Indicates that one entity holds a familial or kinship-based role in relation to another entity.
-
C.
hasLineageRole
Indicates a relationship where an entity holds a specific role or function within a lineage, ancestry, or genealogical chain.
-
D.
hasHereditaryRights
Indicates that one entity possesses rights or privileges that are passed down through family lineage or inheritance from another entity.
-
E.
hasRoleInSuccession
chosen
Indicates that an entity holds a specific role or position within a defined line or order of succession.
- 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_69ef5381f2648190a2392d0fab833095 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 27, 2026, 12:58 p.m.