Triple
T27900882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Fishdam Ford |
E705629
|
entity |
| Predicate | tookPlaceInColony |
P163755
|
FINISHED |
| Object | Province of South 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: Province of South Carolina | Statement: [Battle of Fishdam Ford, tookPlaceInColony, Province of South Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookPlaceInColony Context triple: [Battle of Fishdam Ford, tookPlaceInColony, Province of South Carolina]
-
A.
hadColonyOn
Indicates that one entity established or possessed a colony located on another entity (typically a territory, planet, or celestial body).
-
B.
colonyOf
Indicates that one entity is a colony belonging to, founded by, or politically dependent on another entity.
-
C.
endedInMainColony
Indicates that an event, process, or entity concluded within the primary or central colony rather than elsewhere.
-
D.
colonyLocatedIn
Indicates that a colony is geographically or administratively situated within a specified larger area or jurisdiction.
-
E.
operatedInColony
Indicates that an entity conducted operations or activities within a specific colony.
- F. None of above. chosen
Provenance (4 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63c045bd081908e0cb2a119202e8f |
completed | May 2, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63b3039808190b00bbd19161487f3 |
completed | May 2, 2026, 5:58 p.m. |
Created at: April 27, 2026, 6:41 p.m.