Triple
T9703903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Union NUTS 3 region |
E234848
|
entity |
| Predicate | mayCorrespondTo |
P25442
|
FINISHED |
| Object | province |
—
|
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: province | Statement: [European Union NUTS 3 region, mayCorrespondTo, province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayCorrespondTo Context triple: [European Union NUTS 3 region, mayCorrespondTo, province]
-
A.
mayCoordinate
Indicates that one entity is permitted or has the option to coordinate or work jointly with another entity.
-
B.
partiallyCorrespondsTo
chosen
Indicates that one entity matches or aligns with another entity only in some aspects, segments, or components, rather than fully or exactly.
-
C.
mayPresent
Indicates that one entity is permitted or authorized to present, display, or introduce another entity or item.
-
D.
mayMeet
Indicates that one entity is permitted or has the possibility to meet or come together with another entity.
-
E.
mayReferMattersTo
Indicates that one party has the option or authority to direct or escalate certain issues, cases, or concerns to another party or body for consideration or action.
- 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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d73a0148190ad4178fd462cdd9c |
completed | April 1, 2026, 10:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03b641408190942464eaf174c6b5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:18 p.m.