Triple
T9732791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mulberry Grove plantation |
E235985
|
entity |
| Predicate | siteOfInvention |
P33964
|
FINISHED |
| Object | cotton gin |
—
|
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: cotton gin | Statement: [Mulberry Grove plantation, siteOfInvention, cotton gin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siteOfInvention Context triple: [Mulberry Grove plantation, siteOfInvention, cotton gin]
-
A.
wasInventedBy
Indicates that something (typically an object, concept, or process) was created or brought into existence by a particular inventor or originator.
-
B.
wasInventedInYear
Indicates that an entity was created or invented in a specific calendar year.
-
C.
firstDeveloped
Indicates that one entity was the earliest to create, originate, or bring another entity into existence.
-
D.
placeOfDevelopment
chosen
Indicates the location where something (such as a product, project, or work) was created, designed, or developed.
-
E.
invention
Indicates that one entity is the creator or originator of another entity, typically a device, method, or idea.
- 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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9eb3d6e4819090b3c7fb92550c57 |
completed | April 1, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:22 p.m.