Triple
T5766707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FMD |
E127232
|
entity |
| Predicate | outputUsedFor |
P63101
|
FINISHED |
| Object | trigger decisions |
—
|
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: trigger decisions | Statement: [FMD, outputUsedFor, trigger decisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outputUsedFor Context triple: [FMD, outputUsedFor, trigger decisions]
-
A.
outputUsedBy
Indicates that a particular output produced by one entity is consumed, referenced, or otherwise utilized by another entity.
-
B.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
-
D.
usedResource
Indicates that an entity has utilized or consumed a particular resource in performing an action or achieving a result.
-
E.
resultUsage
chosen
Indicates how the outcome or result of an action, process, or event is used, applied, or consumed in relation to another entity or context.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021ce8d3c81909b332cb1c33a61ad |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.