Triple
T26647803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolærne |
E668966
|
entity |
| Predicate | historicalPeriodOfMilitaryUse |
P136735
|
FINISHED |
| Object | 20th 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: 20th century | Statement: [Bolærne, historicalPeriodOfMilitaryUse, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodOfMilitaryUse Context triple: [Bolærne, historicalPeriodOfMilitaryUse, 20th century]
-
A.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
B.
militaryHistoryTopic
Indicates that there exists a relationship where the subject is a topic, theme, or subject matter specifically concerned with military history.
-
C.
hasMilitarySignificanceSince
Indicates that something has held military importance or strategic value starting from a specified point in time.
-
D.
eraOfPrimaryMilitaryUse
chosen
Indicates the historical time period during which the subject was primarily used for military purposes.
-
E.
historicalEquipment
Indicates that an entity is or involves equipment that was used in the past, typically in a historical or legacy 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_69ee9d00eb5481908d6c6d0ada2f0c9a |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 27, 2026, 2:32 a.m.