Triple
T21107681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maps and Politics |
E520091
|
entity |
| Predicate | situatesInField |
P83026
|
FINISHED |
| Object | political geography |
—
|
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: political geography | Statement: [Maps and Politics, situatesInField, political geography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: situatesInField Context triple: [Maps and Politics, situatesInField, political geography]
-
A.
locationOnField
Indicates the specific position or area that an entity occupies on a defined field or playing surface.
-
B.
positionInField
chosen
Indicates the specific role, location, or functional placement an entity occupies within a defined field, domain, or area of activity.
-
C.
centeredOnField
Indicates that one entity is positioned or focused around the central area of a specified field or domain.
-
D.
hasInfield
Indicates that an entity possesses or includes a designated infield area, typically within a larger spatial or structural context.
-
E.
definedInField
Indicates that something (such as a concept, method, or element) is formally specified, declared, or established within a particular field, domain, or area of study.
- 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_69e0b509a318819092fbbcb21d1fe603 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e720fe800c81909edf215c5f1f27c2 |
completed | April 21, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_69e5dbff56848190a03b350a9305c612 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:53 p.m.