Triple
T19153137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina Unionists |
E468857
|
entity |
| Predicate | includedClass |
P56991
|
FINISHED |
| Object | white North Carolinians |
—
|
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: white North Carolinians | Statement: [North Carolina Unionists, includedClass, white North Carolinians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedClass Context triple: [North Carolina Unionists, includedClass, white North Carolinians]
-
A.
includesClasses
Indicates that one entity contains or encompasses one or more class-type entities as part of its definition or structure.
-
B.
includedBy
chosen
Indicates that one entity is contained within, encompassed by, or treated as a subset or member of another entity.
-
C.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
-
D.
includesInfraclass
Indicates that one entity is classified as belonging to a specific infraclass within a taxonomic hierarchy.
-
E.
usesClass
Indicates that one entity makes use of, depends on, or is implemented using a particular class in its structure or behavior.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eeb7575c8190b52a9d2bde5ac288 |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.