Triple
T7608538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky and Illinois |
E180172
|
entity |
| Predicate | shareEconomicTiesIn |
P9483
|
FINISHED |
| Object | 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: agriculture | Statement: [Kentucky and Illinois, shareEconomicTiesIn, agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareEconomicTiesIn Context triple: [Kentucky and Illinois, shareEconomicTiesIn, agriculture]
-
A.
isLinkedEconomicallyTo
chosen
Indicates that two entities are connected through economic relationships such as trade, investment, financial flows, or shared market dependencies.
-
B.
sharesMotifsWith
Indicates that two entities contain or employ similar recurring themes, patterns, or symbolic elements.
-
C.
connectsCapital
Indicates a relationship where one entity serves as the capital city that is officially linked to or associated with another entity, such as a country or region.
-
D.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
E.
sharesSovereignWith
Indicates that two entities are under the authority of the same sovereign state or ruler.
- 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_69c69f3567008190ab01d2ca7b53584a |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6fa1f6e888190ac6580724803fbc3 |
completed | March 27, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:54 p.m.