Triple
T28846136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LLD |
E728459
|
entity |
| Predicate | honoraryUse |
P173390
|
FINISHED |
| Object | awarded for distinguished contributions to law |
—
|
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: awarded for distinguished contributions to law | Statement: [LLD, honoraryUse, awarded for distinguished contributions to law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honoraryUse Context triple: [LLD, honoraryUse, awarded for distinguished contributions to law]
-
A.
honorificUse
Indicates that one entity refers to or addresses another using an honorific title or respectful linguistic form.
-
B.
honourOf
Indicates that one entity is the source, bearer, or cause of another entity’s honor, prestige, or distinguished recognition.
-
C.
isMostlyHonorary
Indicates that a role, title, or position is primarily symbolic or ceremonial, with little substantive power or responsibility.
-
D.
honoraryPrefix
Indicates that one entity serves as an honorific title or respectful prefix attached to the name of another entity.
-
E.
honorificUsage
Indicates that one entity refers to or addresses another using an honorific title or respectful linguistic form.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: April 28, 2026, 6:42 a.m.