Triple
T25295284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helena, Arkansas |
E634199
|
entity |
| Predicate | hasHistoricProgram |
P169514
|
FINISHED |
| Object | King Biscuit Time |
—
|
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: King Biscuit Time | Statement: [Helena, Arkansas, hasHistoricProgram, King Biscuit Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricProgram Context triple: [Helena, Arkansas, hasHistoricProgram, King Biscuit Time]
-
A.
hasHistoricMP
Indicates that an entity is or has been represented by a specific Member of Parliament at some point in the past.
-
B.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
C.
hasHistoricPlanning
Indicates that an entity has been subject to one or more planning decisions, applications, or designations of historic or heritage significance.
-
D.
hasHistoricFeatures
Indicates that something possesses characteristics, elements, or attributes of historical significance.
-
E.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
- F. None of above. chosen
Provenance (4 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f67fc237608190b6542b56038a7fe4 |
completed | May 2, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f0353c88190a05b2db449abe0f4 |
completed | May 2, 2026, 10:47 p.m. |
Created at: April 21, 2026, 1:22 p.m.