Triple
T26103885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian Order of Merit for Labour |
E658485
|
entity |
| Predicate | titleOfRecipient |
P12204
|
FINISHED |
| Object | Cavaliere del Lavoro |
—
|
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: Cavaliere del Lavoro | Statement: [Italian Order of Merit for Labour, titleOfRecipient, Cavaliere del Lavoro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleOfRecipient Context triple: [Italian Order of Merit for Labour, titleOfRecipient, Cavaliere del Lavoro]
-
A.
recipientTitleUsage
Indicates how a title or honorific is used when addressing or referring to the recipient in the context of the relationship or action.
-
B.
recipientTitleRequired
Indicates that specifying the title of the recipient is mandatory for this relationship or action to be valid.
-
C.
receivedTitle
chosen
Indicates that an entity has been formally granted or awarded a specific title or honor.
-
D.
titleHolderName
Indicates the name of the person or entity that holds a particular title or position.
-
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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 26, 2026, 7:57 p.m.