Triple
T37977097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lumbee tribal territory |
E947452
|
entity |
| Predicate | coreCounty |
P5971
|
FINISHED |
| Object | Robeson County, North Carolina |
—
|
NE NERFINISHED |
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: Robeson County, North Carolina | Statement: [Lumbee tribal territory, coreCounty, Robeson County, North Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreCounty Context triple: [Lumbee tribal territory, coreCounty, Robeson County, North Carolina]
-
A.
inCounty
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
-
B.
homeCounty
Indicates that a specified county is the primary home or place of residence for a given person or entity.
-
C.
cityCounty
Indicates that a city is located within, and administratively belongs to, a specific county.
-
D.
includesCounty
chosen
Indicates that a larger geographic or administrative region contains or encompasses a specific county within its boundaries.
-
E.
majorCounty
Indicates that a county holds primary or significant administrative, economic, or demographic importance within a larger region or jurisdiction.
- 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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.