Triple
T21640046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mechanical Engineering Division |
E534066
|
entity |
| Predicate | employsProfession |
P69514
|
FINISHED |
| Object | mechanical engineers |
—
|
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: mechanical engineers | Statement: [Mechanical Engineering Division, employsProfession, mechanical engineers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employsProfession Context triple: [Mechanical Engineering Division, employsProfession, mechanical engineers]
-
A.
subjectOccupation
Indicates that the subject holds or performs a particular job, profession, or role as their occupation.
-
B.
leftProfession
Indicates that an entity has stopped or abandoned a particular profession or occupation they previously held.
-
C.
memberProfession
Indicates that a member or individual holds or practices a particular profession or occupation.
-
D.
includesProfession
chosen
Indicates that one entity’s set of attributes, roles, or members contains a specific profession as part of it.
-
E.
occupationType
Indicates the specific kind or category of work, profession, or role that an entity performs or holds.
- 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_69e0c465ae7481908577b7209fdb2a77 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef5390ba7481908f58230779e5b7bb |
completed | April 27, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:35 p.m.