Triple
T8748541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iredell |
E207893
|
entity |
| Predicate | hasDerivedToponym |
P53681
|
FINISHED |
| Object | Iredell 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: Iredell County, North Carolina | Statement: [Iredell, hasDerivedToponym, Iredell County, North Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDerivedToponym Context triple: [Iredell, hasDerivedToponym, Iredell County, North Carolina]
-
A.
hasToponymicDerivatives
chosen
Indicates that a name or term serves as the source from which related place-based or toponymic names are derived.
-
B.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of another entity.
-
C.
hasToponymicForm
Indicates that one entity is a toponymic (place-name-based) form or variant derived from another entity.
-
D.
hasTypeOfToponym
Indicates that one entity is classified as a specific type or category of toponym (place name) in relation to another entity.
-
E.
hasToponymicQualifier
Indicates that an entity is associated with a specific place-related qualifier (toponym) used to distinguish it from other, similarly named entities.
- 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_69ca835bb2bc819084bb5906cb6ef7f8 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5da4214881908b6917f847c43cb5 |
completed | March 31, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:39 p.m.