Triple
T3723445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Belgium |
E81692
|
entity |
| Predicate | titleHoldersAre |
P28721
|
FINISHED |
| Object | members of the House of Belgium |
—
|
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: members of the House of Belgium | Statement: [Prince of Belgium, titleHoldersAre, members of the House of Belgium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHoldersAre Context triple: [Prince of Belgium, titleHoldersAre, members of the House of Belgium]
-
A.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
B.
titleHolderName
Indicates the name of the person or entity that holds a particular title or position.
-
C.
titleHolderIsUsually
chosen
Indicates that an entity serving as a title holder is typically or most commonly a particular type or category of entity.
-
D.
titleHolderUnder
Indicates that one entity holds a title, position, or rank under the authority, jurisdiction, or hierarchy of another entity.
-
E.
titleHolderTo
Indicates that one entity currently holds or possesses an official title, position, or designation in relation to 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_69ad8b1b7ef081908d2d381bbf54985a |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcaf3f2ec8190a3a8f363cfb762f3 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc0436e508190909ec4a3e8443aef |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.