Triple
T2690862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas's 28th congressional district |
E58397
|
entity |
| Predicate | hasBorderOrientation |
P37328
|
FINISHED |
| Object | south |
—
|
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: south | Statement: [Texas's 28th congressional district, hasBorderOrientation, south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderOrientation Context triple: [Texas's 28th congressional district, hasBorderOrientation, south]
-
A.
hasBorderDirection
chosen
Indicates that one entity’s border lies in, or is oriented toward, a specified cardinal or relative direction with respect to another entity.
-
B.
hasOrientation
Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
-
C.
hasBorderRole
Indicates that an entity holds a specific functional or administrative role related to a border or boundary between regions or jurisdictions.
-
D.
hasBorderRelation
Indicates that one entity shares a boundary or border with another entity.
-
E.
hasBorderConnection
Indicates that two regions or entities share a common boundary or are directly connected along a border.
- 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda0cb9b48190ab354c277cef9e23 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81c9b4c81908e5e0da6ac5f828b |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.