Triple
T25440007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petrapole |
E637476
|
entity |
| Predicate | countryOnOppositeSide |
P86312
|
FINISHED |
| Object | Bangladesh |
—
|
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: Bangladesh | Statement: [Petrapole, countryOnOppositeSide, Bangladesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOnOppositeSide Context triple: [Petrapole, countryOnOppositeSide, Bangladesh]
-
A.
borderingCountryOnOtherSide
Indicates that one country lies on the opposite side of a shared border relative to another country.
-
B.
countryOnOneSide
Indicates that one entity is located on one side or border of a specified country.
-
C.
countryOnAxisSide
Indicates that a country was aligned with or belonged to the Axis side in a particular conflict or war.
-
D.
countryOnOtherSide
chosen
Indicates that one location is situated across a boundary or dividing feature (such as a border, river, or sea) from another country, on the opposite side.
-
E.
sovereignStateOnOtherSide
Indicates that one sovereign state is located on the opposite side of a specified reference (such as a border, body of water, or geographic feature) from another sovereign state.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 21, 2026, 2 p.m.