Triple
T32025667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engineers Day in India |
E817809
|
entity |
| Predicate | primaryHonoureeOccupation |
P18120
|
FINISHED |
| Object | civil engineer |
—
|
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: civil engineer | Statement: [Engineers Day in India, primaryHonoureeOccupation, civil engineer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryHonoureeOccupation Context triple: [Engineers Day in India, primaryHonoureeOccupation, civil engineer]
-
A.
honouredPersonOccupation
chosen
Indicates that the honored person is or was associated with a particular occupation or professional role.
-
B.
honoreeRole
Indicates the specific role, title, or capacity in which an individual is being honored in relation to an award, event, or recognition.
-
C.
honoreeKnownFor
Indicates that an honoree is recognized or celebrated specifically for a particular work, achievement, contribution, or notable attribute.
-
D.
namedPersonOccupation
Indicates that a person is explicitly identified as having a particular occupation or job role.
-
E.
laureateOccupation
Indicates the professional role or field in which a laureate is recognized or has worked.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:17 a.m.