Triple
T38404676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Birthplace of the Tomato |
E900991
|
entity |
| Predicate | isPromotionalNicknameFor |
P28716
|
FINISHED |
| Object | Reynoldsburg, Ohio |
—
|
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: Reynoldsburg, Ohio | Statement: [The Birthplace of the Tomato, isPromotionalNicknameFor, Reynoldsburg, Ohio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPromotionalNicknameFor Context triple: [The Birthplace of the Tomato, isPromotionalNicknameFor, Reynoldsburg, Ohio]
-
A.
isPromotedAs
Indicates that one entity is advertised, marketed, or presented to others in a particular way or role by another entity.
-
B.
isNickname
chosen
Indicates that one name is an informal or alternative name commonly used to refer to the same person or entity as another name.
-
C.
arePromotedBy
Indicates that one entity advances in rank, position, or status as a result of an action or decision made by another entity.
-
D.
hasPromotionalSingle
Indicates that an entity has an associated promotional single released to market or media for promotional purposes.
-
E.
hasPromotionStyle
Indicates the manner or approach used to promote or market something in relation to 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.