Triple
T13118795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vadsøya cultural heritage area |
E311668
|
entity |
| Predicate | hasPeriodRepresented |
P58089
|
FINISHED |
| Object | 19th century coastal settlement |
—
|
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: 19th century coastal settlement | Statement: [Vadsøya cultural heritage area, hasPeriodRepresented, 19th century coastal settlement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPeriodRepresented Context triple: [Vadsøya cultural heritage area, hasPeriodRepresented, 19th century coastal settlement]
-
A.
hasPeriodRange
Indicates that there is a temporal span or interval during which something is valid, active, or applicable.
-
B.
hasHistoryPeriod
chosen
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
C.
isSetInTimePeriod
Indicates that an event, story, or situation takes place within a specified time period.
-
D.
hasCollectionFromPeriod
Indicates that a collection originates from, or is associated with, a specific historical or temporal period.
-
E.
refersToPeriod
Indicates that one entity designates, references, or is associated with a specific time period or interval.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98182011c8190a504678affbb7787 |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:06 p.m.