Triple
T32872226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MND-SE |
E840822
|
entity |
| Predicate | allianceRegion |
P31610
|
FINISHED |
| Object | NATO southeastern region |
—
|
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: NATO southeastern region | Statement: [MND-SE, allianceRegion, NATO southeastern region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allianceRegion Context triple: [MND-SE, allianceRegion, NATO southeastern region]
-
A.
participantsRegion
Indicates that the related entities are associated with, originate from, or operate within a specified geographic region.
-
B.
clubRegion
Indicates that a club is located in, associated with, or belongs to a particular geographic region.
-
C.
ITURegion
Indicates the International Telecommunication Union (ITU) regional classification to which an entity (such as a location or station) belongs.
-
D.
ISORegion
Indicates a standardized geographic or administrative region as defined by an ISO (International Organization for Standardization) code.
-
E.
hasRegionalAffiliation
chosen
Indicates that an entity is associated with, belongs to, or is officially linked to a specific geographic region.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:17 a.m.