Triple
T12853587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina–South Carolina border |
E307389
|
entity |
| Predicate | reSurveyedIn |
P42127
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [North Carolina–South Carolina border, reSurveyedIn, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reSurveyedIn Context triple: [North Carolina–South Carolina border, reSurveyedIn, 18th century]
-
A.
surveyedFor
Indicates that one entity has been examined, questioned, or assessed in order to gather information specifically about another entity or topic.
-
B.
surveyedIn
chosen
Indicates that an entity was included as part of the scope or coverage of a particular survey or data-collection effort.
-
C.
coSurveyedWith
Indicates that two or more entities participated together in the same survey activity or data-collection effort.
-
D.
surveyed
Indicates that one entity systematically examined, questioned, or measured another entity or group to gather information or assess a situation.
-
E.
reassessedAfter
Indicates that one entity is evaluated or reviewed again at a time point that occurs after another specified event or assessment.
- 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_69d7bdf5e7cc8190be357278bc5ba3bb |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa3002881908000357b1f95a3ac |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:36 p.m.