Triple
T17447315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFDSM |
E424818
|
entity |
| Predicate | meritLevel |
P8804
|
FINISHED |
| Object | exceptional |
—
|
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: exceptional | Statement: [AFDSM, meritLevel, exceptional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meritLevel Context triple: [AFDSM, meritLevel, exceptional]
-
A.
honorLevel
Indicates the degree or status of respect, distinction, or recognition accorded to an entity relative to others.
-
B.
medalHierarchyLevel
Indicates the relative rank or position of a medal within an ordered hierarchy of medals.
-
C.
disciplineLevel
Indicates the degree or strictness of control, order, or self-regulation applied in a given context or relationship.
-
D.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
E.
achievementLevel
chosen
Indicates the degree or extent to which an entity has attained a particular goal, standard, or performance outcome.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44ffc89e4819096372cc55b40cc3b |
completed | April 19, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.