Triple
T9841187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fellow of the American Society of Mechanical Engineers |
E239228
|
entity |
| Predicate | typicalAwardedTo |
P58949
|
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: [Fellow of the American Society of Mechanical Engineers, typicalAwardedTo, mechanical engineers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAwardedTo Context triple: [Fellow of the American Society of Mechanical Engineers, typicalAwardedTo, mechanical engineers]
-
A.
typicalAwardedBy
Indicates the usual or standard agent (such as a person or organization) that confers or grants a particular award.
-
B.
typicalAwardType
Indicates the usual or most common type or category of award associated with a given entity or context.
-
C.
typicalAwardDate
Indicates the date on which an award is customarily or normally given or conferred.
-
D.
typicalLaureateType
Indicates the usual or most common type or category of laureate associated with something.
-
E.
typicalHonoree
chosen
Indicates that an entity is the usual or characteristic recipient of an honor, award, or recognition associated with 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb34c920c81909b56ed9936b15f9b |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.