Triple
T2793514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red River (southeastern boundary area) |
E61981
|
entity |
| Predicate | usedAsBoundarySince |
P2935
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Red River (southeastern boundary area), usedAsBoundarySince, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsBoundarySince Context triple: [Red River (southeastern boundary area), usedAsBoundarySince, 19th century]
-
A.
usedSince
chosen
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
-
B.
hasBoundaryFeature
Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
-
C.
setsBoundary
Indicates that one entity defines or forms the limiting edge or border of another entity.
-
D.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
E.
hasConceptualBoundary
Indicates that one entity defines, marks, or establishes the abstract limit or scope of another entity’s meaning, applicability, or conceptual extent.
- 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_69ab4b7f51d881908768300ebd2fbdae |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddd33610819085ac7c5bec0e6af0 |
completed | March 7, 2026, 8:12 a.m. |
| PD | Predicate disambiguation | batch_69abdd040f9481908e9c7a2df88ea1ae |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.