Triple
T35455795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval General Service Medal |
E1024768
|
entity |
| Predicate | totalClaspsAuthorized |
P189750
|
FINISHED |
| Object | 231 |
—
|
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: 231 | Statement: [Naval General Service Medal, totalClaspsAuthorized, 231]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalClaspsAuthorized Context triple: [Naval General Service Medal, totalClaspsAuthorized, 231]
-
A.
hasClasps
Indicates that one entity is equipped with or features clasps that fasten, secure, or attach it to another entity or its parts.
-
B.
clasps
Indicates that one entity grips, holds, or fastens onto another firmly, often by closing around it.
-
C.
hasClearanceWhenClosed
Indicates that an entity retains or possesses the specified clearance level even when it is in a closed or inactive state.
-
D.
numberOfCapsules
Indicates the quantity or count of capsules associated with an entity or event.
-
E.
hasClearanceWhenOpen
Indicates that an entity possesses the required clearance or authorization specifically during the time or condition when something (e.g., a resource, facility, or system) is open or accessible.
- F. None of above. chosen
Provenance (4 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_69f76df92f108190817222e520e22268 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc9d0854c8190aa00093274afebb8 |
completed | May 6, 2026, 11:08 p.m. |
Created at: May 3, 2026, 4:04 p.m.