Triple
T22042720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Peanut Capital of the World |
E544678
|
entity |
| Predicate | highlightsRoleIn |
P117092
|
FINISHED |
| Object | peanut industry |
—
|
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: peanut industry | Statement: [The Peanut Capital of the World, highlightsRoleIn, peanut industry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highlightsRoleIn Context triple: [The Peanut Capital of the World, highlightsRoleIn, peanut industry]
-
A.
highlightsRole
chosen
Indicates that one entity emphasizes, showcases, or draws special attention to the role or function of another entity.
-
B.
socialRoleEmphasis
Indicates an emphasis on or prioritization of a particular social role within a relationship or interaction.
-
C.
highlightsSign
Indicates that one entity visually emphasizes or draws special attention to a sign.
-
D.
isMajorHighlightOf
Indicates that something serves as a primary or especially notable feature, event, or focal point within a larger context or whole.
-
E.
highlightsAttributeOf
Indicates that one entity draws attention to, emphasizes, or showcases a particular attribute or property of 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1282ac42c819099b2f664f79f5b83 |
completed | April 28, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:25 p.m.