Triple
T30312466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rugby, North Dakota |
E770963
|
entity |
| Predicate | hasGeographicClaim |
P135616
|
FINISHED |
| Object | geographic center of North America |
—
|
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: geographic center of North America | Statement: [Rugby, North Dakota, hasGeographicClaim, geographic center of North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeographicClaim Context triple: [Rugby, North Dakota, hasGeographicClaim, geographic center of North America]
-
A.
geographicScopeClaimed
chosen
Indicates the geographic area or territory that an entity asserts or claims as being within its scope, authority, or coverage.
-
B.
hasGeographicBasis
Indicates that something is grounded in, derived from, or defined by a particular geographic location or area.
-
C.
hasGeographicType
Indicates that an entity is associated with or classified by a specific type or category of geographic feature or area.
-
D.
isGeographicallySpecific
Indicates that something is limited to or uniquely associated with a particular geographic location or area.
-
E.
isGeographicTitle
Indicates that a title or designation specifically refers to a geographic location or region.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 29, 2026, 7:50 p.m.