Triple
T34320643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | van Holland |
E880725
|
entity |
| Predicate | hasRegionOfReference |
P66507
|
FINISHED |
| Object | North Holland |
E24160
|
NE 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: North Holland | Statement: [van Holland, hasRegionOfReference, North Holland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionOfReference Context triple: [van Holland, hasRegionOfReference, North Holland]
-
A.
regionReference
chosen
Indicates that one entity refers to, points to, or is associated with a specific region or area defined by another entity.
-
B.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
C.
isRegionOf
Indicates that one entity is a geographic or administrative region belonging to, contained within, or associated with another entity.
-
D.
refersToStateInRegion
Indicates that one entity denotes or references a specific state located within a particular region.
-
E.
hasRegionalEntity
Indicates that one entity includes, governs, or is associated with another entity that functions as its regional subdivision or component.
- F. None of above.
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_69f349b9cd508190a996a616903b3e6d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37211c0e388190b34c45c56a90c576 |
completed | June 20, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:57 a.m.