Triple
T37639055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | provinces of the Low Countries |
E936565
|
entity |
| Predicate | containedTerritory |
P65771
|
FINISHED |
| Object | County of Flanders |
E214371
|
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: County of Flanders | Statement: [provinces of the Low Countries, containedTerritory, County of Flanders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containedTerritory Context triple: [provinces of the Low Countries, containedTerritory, County of Flanders]
-
A.
territoryIncluded
Indicates that one territory is geographically or administratively contained within another territory.
-
B.
containedTerrane
Indicates that one geological terrane is spatially contained within the boundaries of another terrane.
-
C.
territoryOriginallyIncluded
Indicates that an earlier or original territorial boundary encompassed the referenced area or entity.
-
D.
includedTerritoryType
Indicates that one territory type is contained within, or forms part of, another territory type.
-
E.
partOfTerritory
chosen
Indicates that one geographic or administrative area is contained within, and forms a constituent portion of, another territory.
- 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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a01bb9c33cc8190a95ba124d97edf99 |
completed | May 11, 2026, 11:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40cdad509c8190a90a14a7dd5d9358 |
completed | June 28, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_6a01bb6772148190a243d1141ad0a237 |
completed | May 11, 2026, 11:20 a.m. |
Created at: May 3, 2026, 4:18 p.m.