Triple
T29919500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rear-Admiral of the Red |
E759882
|
entity |
| Predicate | typicalTimeframe |
P139699
|
FINISHED |
| Object | 17th to 19th centuries |
—
|
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: 17th to 19th centuries | Statement: [Rear-Admiral of the Red, typicalTimeframe, 17th to 19th centuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTimeframe Context triple: [Rear-Admiral of the Red, typicalTimeframe, 17th to 19th centuries]
-
A.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
B.
timeframeApproximate
Indicates that the time period associated with an event or relation is not exact but only roughly or loosely specified.
-
C.
typicalPeriodRange
chosen
Indicates the usual or most commonly observed range of time intervals associated with an event, process, or state.
-
D.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
E.
timeframeOfUse
Indicates the period or duration during which something is intended, allowed, or expected to be used.
- 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_69f2246189fc8190996b63ee1f9a2374 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a0316136a14819085bb88563d5abc42 |
completed | May 12, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_6a03158a962c81909f17d58197f6ba00 |
completed | May 12, 2026, 11:56 a.m. |
Created at: April 29, 2026, 6:14 p.m.