Triple
T35455769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval General Service Medal |
E1024768
|
entity |
| Predicate | dateRangeOfActionsRecognised |
P9341
|
FINISHED |
| Object | 1793–1840 |
—
|
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: 1793–1840 | Statement: [Naval General Service Medal, dateRangeOfActionsRecognised, 1793–1840]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateRangeOfActionsRecognised Context triple: [Naval General Service Medal, dateRangeOfActionsRecognised, 1793–1840]
-
A.
supportsDateRestrictions
Indicates that an entity can enforce or handle constraints based on specific dates or date ranges.
-
B.
typicalEndDateRange
Indicates the usual or expected range of end dates associated with an event, activity, or time-bounded entity.
-
C.
collectionTimespan
chosen
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
-
D.
occurredBetween
Indicates that an event or action took place within the time interval defined by two temporal boundaries.
-
E.
timePeriodRecognized
Indicates that a specific span of time has been formally identified or acknowledged as significant or valid within a given 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_69f76df92f108190817222e520e22268 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.