Triple
T33404886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordan |
E855411
|
entity |
| Predicate | WorldBankRegion |
P40571
|
FINISHED |
| Object | Middle East and North Africa |
—
|
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: Middle East and North Africa | Statement: [Jordan, WorldBankRegion, Middle East and North Africa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WorldBankRegion Context triple: [Jordan, WorldBankRegion, Middle East and North Africa]
-
A.
WorldBankMember
Indicates that an entity is a member country or organization formally belonging to the World Bank.
-
B.
worldRegion
chosen
Indicates that one entity is a geographic region that encompasses, contains, or is associated with the other entity within the world.
-
C.
developedRegion
Indicates that a specified region has been developed, typically through economic growth, infrastructure, or urbanization, as a result of some agent or process.
-
D.
developmentRegion
Indicates the geographic or administrative region in which something is developed, produced, or primarily created.
-
E.
ISORegion
Indicates a standardized geographic or administrative region as defined by an ISO (International Organization for Standardization) code.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: May 1, 2026, 1:36 a.m.