Triple
T30242082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pagus Flandrensis |
E768944
|
entity |
| Predicate | hasCoreAreaOf |
P58897
|
FINISHED |
| Object | later County of Flanders |
—
|
NE NERFINISHED |
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: later County of Flanders | Statement: [pagus Flandrensis, hasCoreAreaOf, later County of Flanders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoreAreaOf Context triple: [pagus Flandrensis, hasCoreAreaOf, later County of Flanders]
-
A.
hasCoreArea
Indicates that an entity possesses a primary or central area that is fundamental to its structure, function, or focus.
-
B.
coreAreaOf
chosen
Indicates that one entity is the central, primary, or most important area or domain of focus for another entity.
-
C.
hasSubstantiveArea
Indicates that one entity is associated with, or falls within, a particular substantive field or domain of activity, knowledge, or regulation.
-
D.
protectedAreaCore
Indicates that an entity lies within the core, most strictly protected zone of a designated protected area.
-
E.
hasCoreTown
Indicates that an entity possesses or is associated with a primary or central town that serves as its main urban center.
- 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_69f224820c048190b1435c4cc145acf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a01203ac018819085d7c9abd8345b23 |
completed | May 11, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_6a011f3f149c819090749722da0e3413 |
completed | May 11, 2026, 12:13 a.m. |
Created at: April 29, 2026, 7:39 p.m.