Triple
T8502363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Everglades Plantation Company |
E201249
|
entity |
| Predicate | usedLandFor |
P50683
|
FINISHED |
| Object | plantation agriculture |
—
|
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: plantation agriculture | Statement: [Everglades Plantation Company, usedLandFor, plantation agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedLandFor Context triple: [Everglades Plantation Company, usedLandFor, plantation agriculture]
-
A.
usedToCreateLand
Indicates that something served as a means, material, or method for producing or forming a particular piece of land.
-
B.
usedAgriculture
chosen
Indicates that an entity employed agricultural methods, practices, or resources for cultivation, production, or related purposes.
-
C.
otherLandUse
Indicates that the land is used for purposes that do not fall into any of the primary or predefined land-use categories.
-
D.
majorLandUse
Indicates the primary way a given area of land is utilized or designated (e.g., residential, commercial, agricultural).
-
E.
formerLandUse
Indicates the type of land use that characterized a location prior to its current or present use.
- 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_69ca831fe47c8190b5c57b456d2aefa0 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe59c413881909513d8a9d52333c0 |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:14 p.m.