Triple
T24825758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander of the Order of Military Merit |
E621184
|
entity |
| Predicate | for |
P157382
|
FINISHED |
| Object | outstanding leadership |
—
|
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: outstanding leadership | Statement: [Commander of the Order of Military Merit, for, outstanding leadership]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: for Context triple: [Commander of the Order of Military Merit, for, outstanding leadership]
-
A.
for
chosen
Indicates a relationship in which something is intended for, directed toward, benefiting, or associated with a particular entity or purpose.
-
B.
by
Indicates that an action is performed, caused, or authored through the agency, means, or proximity of a specified entity.
-
C.
from
Indicates that something originates, is sent, or is derived from a particular source or starting point.
-
D.
with
Indicates a general associative relationship in which one entity is accompanied by, connected to, or occurring together with another entity.
-
E.
forward
Indicates that one entity sends, directs, or passes something on to another entity, typically along a path or sequence.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:05 a.m.