Triple
T30732129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carolina (colony) |
E782450
|
entity |
| Predicate | includedTerritoryNowIn |
P11790
|
FINISHED |
| Object | 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: North Carolina | Statement: [Carolina (colony), includedTerritoryNowIn, North Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedTerritoryNowIn Context triple: [Carolina (colony), includedTerritoryNowIn, North Carolina]
-
A.
includedTerritoryType
Indicates that one territory type is contained within, or forms part of, another territory type.
-
B.
territoryIncluded
chosen
Indicates that one territory is geographically or administratively contained within another territory.
-
C.
sometimesIncludesTerritory
Indicates that one entity occasionally, but not consistently, encompasses or contains the territory of another entity.
-
D.
territoryOriginallyIncluded
Indicates that an earlier or original territorial boundary encompassed the referenced area or entity.
-
E.
includesTerritorySubjectTo
Indicates that one entity’s territorial scope encompasses another territory that is subject to it.
- 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_69f224ad9f9c81908e02a79ae0001137 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00a094c44c81908e4501151688a635 |
completed | May 10, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_6a009fcdfd848190841deaad9667d347 |
completed | May 10, 2026, 3:10 p.m. |
Created at: April 29, 2026, 8:37 p.m.