Triple
T4577655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Plant City |
E123177
|
entity |
| Predicate | hasSpecialtyCrop |
P54821
|
FINISHED |
| Object | strawberries |
—
|
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: strawberries | Statement: [City of Plant City, hasSpecialtyCrop, strawberries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialtyCrop Context triple: [City of Plant City, hasSpecialtyCrop, strawberries]
-
A.
hasCropSpecies
chosen
Indicates that a particular location, field, or agricultural system is associated with or used to cultivate a specified crop species.
-
B.
hasCultivar
Indicates that one entity is a plant species or variety that possesses, includes, or is associated with a specific cultivated variety (cultivar) as another entity.
-
C.
majorCrop
Indicates that a particular crop is one of the primary or most important crops cultivated in a given area or context.
-
D.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
E.
isCultivatedAs
Indicates that one entity is intentionally grown, tended, or produced by another as a crop, resource, or cultivated organism.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58e153908190ac8f578e03aecdfc |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.