Triple
T14831869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veendam, North Dakota |
E348725
|
entity |
| Predicate | sharesHistoricalConnectionWith |
P3438
|
FINISHED |
| Object | Dutch settlers and heritage |
—
|
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: Dutch settlers and heritage | Statement: [Veendam, North Dakota, sharesHistoricalConnectionWith, Dutch settlers and heritage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesHistoricalConnectionWith Context triple: [Veendam, North Dakota, sharesHistoricalConnectionWith, Dutch settlers and heritage]
-
A.
sharesHistoryWith
chosen
Indicates that two entities have a common or overlapping past, such as shared experiences, events, or origins.
-
B.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
C.
sharesTimelineWith
Indicates that two entities participate in or are associated with the same timeline, sequence of events, or temporal context.
-
D.
historicalContactWith
Indicates that two entities have interacted or been in communication with each other at some point in the past.
-
E.
sharesStatusWith
Indicates that two entities have the same status or state within a given 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded0748eec8190a39c94024c3a3e3e |
completed | April 14, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:52 a.m.