Triple
T31058111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian River region |
E791449
|
entity |
| Predicate | hasIndustryDesignation |
P974
|
FINISHED |
| Object | Indian River citrus |
—
|
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: Indian River citrus | Statement: [Indian River region, hasIndustryDesignation, Indian River citrus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndustryDesignation Context triple: [Indian River region, hasIndustryDesignation, Indian River citrus]
-
A.
hasIspDesignation
Indicates that an entity has been assigned a specific Internet Service Provider (ISP) designation or classification.
-
B.
hasDesignation
chosen
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
C.
hasInternalDesignationFor
Indicates that one entity assigns or uses an internal label, code, or designation to refer to another entity.
-
D.
hasCDDesignation
Indicates that an entity has been assigned a specific CD (cluster of differentiation) designation used to classify cell surface molecules.
-
E.
hasDesignationFor
Indicates that one entity assigns or holds a specific title, label, or formal designation for another entity.
- 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_69f224cb08908190ba71ad9aa87518ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: April 29, 2026, 9 p.m.