Triple
T5762136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IJ |
E127119
|
entity |
| Predicate | historicalType |
P66217
|
FINISHED |
| Object | former bay of Zuiderzee |
—
|
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: former bay of Zuiderzee | Statement: [IJ, historicalType, former bay of Zuiderzee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalType Context triple: [IJ, historicalType, former bay of Zuiderzee]
-
A.
historicalCategory
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
-
B.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another entity.
-
C.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
-
D.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
-
E.
historicalNameType
Indicates that the relationship specifies the type or category of a historical name associated with an entity.
- F. None of above. chosen
Provenance (4 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_69c00833a3fc81908f4bc29ed011b7a6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02939b22c81908f8354ab175d168d |
completed | March 22, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69c021cc68648190bb86d049ebe80f12 |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c028fec2bc819083f5dca6a8d9d435 |
completed | March 22, 2026, 5:38 p.m. |
Created at: March 22, 2026, 3:49 p.m.