Triple
T19448563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Corps Good Conduct Medal |
E486549
|
entity |
| Predicate | minimumRank |
P16384
|
FINISHED |
| Object | enlisted |
—
|
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: enlisted | Statement: [Marine Corps Good Conduct Medal, minimumRank, enlisted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumRank Context triple: [Marine Corps Good Conduct Medal, minimumRank, enlisted]
-
A.
lowestRank
Indicates that the subject has the least or worst rank in an ordered set compared to all other related entities.
-
B.
highestRankIn
Indicates that one entity holds the top or most senior rank within a specified group, category, or context relative to other entities.
-
C.
containsRank
Indicates that one entity includes or encompasses another entity that has a specific rank or hierarchical level within it.
-
D.
eligibleRank
chosen
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
E.
canonicalRank
Indicates the standard or officially recognized rank or level assigned to an entity within an ordered hierarchy.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338be5a48190973d9ecae853900c |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.