Triple
T2727147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bladen County, North Carolina |
E60220
|
entity |
| Predicate | hasReasonForNickname |
P7596
|
FINISHED |
| Object | many other North Carolina counties were formed from its original territory |
—
|
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: many other North Carolina counties were formed from its original territory | Statement: [Bladen County, North Carolina, hasReasonForNickname, many other North Carolina counties were formed from its original territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReasonForNickname Context triple: [Bladen County, North Carolina, hasReasonForNickname, many other North Carolina counties were formed from its original territory]
-
A.
reasonForNickname
chosen
Indicates the explanation or cause behind why a particular nickname was given to an entity.
-
B.
reasonForName
Indicates the explanation or cause behind why an entity has a particular name.
-
C.
isNickname
Indicates that one name is an informal or alternative name commonly used to refer to the same person or entity as another name.
-
D.
isOfficialNicknameOf
Indicates that one name is the formally recognized nickname or informal moniker used to refer to another entity.
-
E.
nameChangeReason
Indicates the reason or justification for a change in an entity’s name.
- 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_69ab4b75cd908190b691ef0d1801acda |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdacffa6481909df37335e8fdd595 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82586f88190a98f60d3247fe2d3 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.