Triple
T19766187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arkansas–Texas border |
E474761
|
entity |
| Predicate | hasSurveyHistory |
P99136
|
FINISHED |
| Object | 19th-century boundary surveys |
—
|
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 boundary surveys | Statement: [Arkansas–Texas border, hasSurveyHistory, 19th-century boundary surveys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurveyHistory Context triple: [Arkansas–Texas border, hasSurveyHistory, 19th-century boundary surveys]
-
A.
surveyedFor
Indicates that one entity has been examined, questioned, or assessed in order to gather information specifically about another entity or topic.
-
B.
coSurveyedWith
Indicates that two or more entities participated together in the same survey activity or data-collection effort.
-
C.
hasHistoryIn
chosen
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
D.
surveyedIn
Indicates that an entity was included as part of the scope or coverage of a particular survey or data-collection effort.
-
E.
usesSurveyPoint
Indicates that an entity relies on or references a specific survey point as a positional or measurement basis in its activity or relationship.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e653232e508190a7d484c0a1e2939a |
completed | April 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:48 p.m.