Triple
T2066811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Low-A West North Division |
E45919
|
entity |
| Predicate | geographicQualifier |
P25535
|
FINISHED |
| Object | North |
—
|
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: North | Statement: [Low-A West North Division, geographicQualifier, North]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicQualifier Context triple: [Low-A West North Division, geographicQualifier, North]
-
A.
geographicContext
Indicates that one entity is situated within, associated with, or characterized by the geographic setting or region defined by another entity.
-
B.
regionName
Indicates the name assigned to a specific geographic or administrative region.
-
C.
arealRegion
chosen
Indicates that something occupies or pertains to a specific two-dimensional geographic or spatial area.
-
D.
hasGeographyCharacteristic
Indicates that an entity possesses a specific geographical feature, property, or attribute.
-
E.
regionallyAssociatedWith
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
- 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_69a8891b38288190abd572ccad9b6928 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9f236f08190b602d337afb1880f |
completed | March 7, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69abb7aee9b48190999620176e3a6ee2 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:40 p.m.