Triple
T19670553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vosmeer van Aemstel |
E472322
|
entity |
| Predicate | centuryOfFictionalSetting |
P18945
|
FINISHED |
| Object | 13th 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: 13th century | Statement: [Vosmeer van Aemstel, centuryOfFictionalSetting, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centuryOfFictionalSetting Context triple: [Vosmeer van Aemstel, centuryOfFictionalSetting, 13th century]
-
A.
fictionalCenturyOfOrigin
Indicates the fictional century in which an entity is depicted as having originated or first appeared within its narrative world.
-
B.
fictionalEra
chosen
Indicates the time period or age within a fictional or imaginary setting in which an entity exists or an event occurs.
-
C.
storySettingDecade
Indicates the decade in which the events or setting of a story take place.
-
D.
fictionalSettingRegion
Indicates that a fictional setting is located within or associated with a specific geographic or administrative region.
-
E.
originalCentury
Indicates the century in which something was originally created, produced, or came into existence.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6416b9cf8819096f44e3f9fbf86fa |
completed | April 20, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69e514eb37b8819091502cc954f70eba |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.