Triple
T31144001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maastricht region |
E793870
|
entity |
| Predicate | hasStatePart |
P16690
|
FINISHED |
| Object | North Rhine-Westphalia |
—
|
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: North Rhine-Westphalia | Statement: [Maastricht region, hasStatePart, North Rhine-Westphalia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatePart Context triple: [Maastricht region, hasStatePart, North Rhine-Westphalia]
-
A.
hasStatePortionIn
chosen
Indicates that a state has a geographic portion or area located within the boundaries of another region or entity.
-
B.
hasStateOf
Indicates that an entity possesses, exhibits, or is currently in a particular condition, status, or mode.
-
C.
hasStateBranch
Indicates that one entity functions as a branch, subdivision, or local office of a larger parent entity within a particular state or regional jurisdiction.
-
D.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
-
E.
hasParticipantStateOrProvince
Indicates that an entity’s participation in an event, activity, or relationship is associated with a specific state or province as its geographic 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: April 29, 2026, 9:06 p.m.