Triple
T37580890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Capitan |
E934953
|
entity |
| Predicate | hasHistoricalSettingCentury |
P168452
|
FINISHED |
| Object | 17th century |
—
|
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 century | Statement: [Le Capitan, hasHistoricalSettingCentury, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalSettingCentury Context triple: [Le Capitan, hasHistoricalSettingCentury, 17th century]
-
A.
isFromCentury
chosen
Indicates that an entity originates from, belongs to, or is associated with a specified century.
-
B.
observedSinceCentury
Indicates that one entity has been observed or documented as existing or occurring since a specified century.
-
C.
hasHistoricHundred
Indicates that an entity has achieved a notable score of 100 (a "hundred") in a historic or particularly significant context.
-
D.
hasHistoricSetting
Indicates that something is set in, or takes place within, a historically significant time period or location.
-
E.
coveredSinceCentury
Indicates that one entity has been covered, coated, or kept under coverage continuously starting from a specified century.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff8aff48988190a48a440de8238ef9 |
completed | May 9, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69ff8a780404819082f48ceb21e7fe11 |
completed | May 9, 2026, 7:26 p.m. |
Created at: May 3, 2026, 4:17 p.m.