Triple
T31127912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ROU |
E793409
|
entity |
| Predicate | codeForCountryInRegion |
P171616
|
FINISHED |
| Object | Eastern Europe |
—
|
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: Eastern Europe | Statement: [ROU, codeForCountryInRegion, Eastern Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeForCountryInRegion Context triple: [ROU, codeForCountryInRegion, Eastern Europe]
-
A.
hasRegionCode
Indicates that an entity is associated with a specific regional identifier or code.
-
B.
regionCodeUsedIn
Indicates that a specific region code is utilized or applied within a particular context, system, or entity.
-
C.
regionCodeType
Indicates the classification or format type used for a given region code within a coding or identification system.
-
D.
countryGridCode
Indicates the standardized grid-based code that identifies the geographic grid cell or area associated with a country.
-
E.
ISO3166-2RegionCode
Indicates the standardized ISO 3166-2 code that specifies the particular primary administrative subdivision (such as a state, province, or region) to which an entity belongs.
- F. None of above. chosen
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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 9:05 p.m.