Triple
T23002956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Markerwaard polder |
E572679
|
entity |
| Predicate | wouldHaveBeenConnectedTo |
P99111
|
FINISHED |
| Object | existing polders in Flevoland |
—
|
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: existing polders in Flevoland | Statement: [Markerwaard polder, wouldHaveBeenConnectedTo, existing polders in Flevoland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wouldHaveBeenConnectedTo Context triple: [Markerwaard polder, wouldHaveBeenConnectedTo, existing polders in Flevoland]
-
A.
formerlyConnectedTo
Indicates that two entities were once connected or associated in some way, but that connection no longer exists.
-
B.
aimedToConnect
chosen
Indicates an intention or effort by one entity to establish a link, relationship, or communication channel with another entity.
-
C.
wouldHaveHadMembers
Indicates a hypothetical or counterfactual relationship in which an entity, under certain conditions or in an unrealized scenario, would have included specific members.
-
D.
notConnectedBy
Indicates that there is no direct link, path, or relationship connecting the referenced entities.
-
E.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f183549bdc81908fdcd44e2c92f7c4 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:50 p.m.