Triple
T3651029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Saint Hubert |
E77416
|
entity |
| Predicate | traditionallyAwardedTo |
P50688
|
FINISHED |
| Object | Catholic princes |
—
|
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: Catholic princes | Statement: [Order of Saint Hubert, traditionallyAwardedTo, Catholic princes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyAwardedTo Context triple: [Order of Saint Hubert, traditionallyAwardedTo, Catholic princes]
-
A.
contractAwardedBy
Indicates that a contract has been formally granted to a party by the specified awarding entity.
-
B.
bidWinner
Indicates that the referenced entity is the winner of a particular bidding or auction process.
-
C.
originallyAwardedTo
Indicates that something (such as a prize, title, or resource) was first granted or assigned to a particular recipient before any later changes or transfers.
-
D.
awardedStatus
Indicates that a particular status, honor, or designation has been formally granted to an entity.
-
E.
awardedIndirectly
Indicates that one entity grants or confers something to another entity through an intermediary or indirect means rather than via a direct award.
- F. None of above. chosen
Provenance (4 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_69ad85def5cc8190863dccf55a18bebb |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc39303bc819090725643e53a96d6 |
completed | March 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69adb84650148190bf79231105e58d7f |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adbae14d488190a6024548979c6faf |
completed | March 8, 2026, 6:07 p.m. |
Created at: March 8, 2026, 3:24 p.m.