Triple
T6206369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulloch County |
E138756
|
entity |
| Predicate | hasLocalEconomyComponent |
P32182
|
FINISHED |
| Object | agribusiness |
—
|
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: agribusiness | Statement: [Bulloch County, hasLocalEconomyComponent, agribusiness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalEconomyComponent Context triple: [Bulloch County, hasLocalEconomyComponent, agribusiness]
-
A.
hasEconomyCharacteristic
Indicates that an economy possesses a particular attribute, feature, or quality.
-
B.
hasNearbyEconomicRegion
Indicates that one economic region is geographically close to or adjacent to another economic region.
-
C.
localEconomyImpact
Indicates the effect that an action, event, or entity has on the economic conditions, activities, or performance of a specific local area or community.
-
D.
hasEconomicOrganization
Indicates that an entity possesses, is associated with, or participates in a specific economic organization or institutional economic structure.
-
E.
regionalEconomyType
chosen
Indicates the type or classification of an economy associated with a specific region.
- 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0626f85748190a94448117a85fd78 |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:20 p.m.