Triple
T19454950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scoops Ahoy |
E486710
|
entity |
| Predicate | hasMenuBoard |
P135978
|
FINISHED |
| Object | flavor list |
—
|
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: flavor list | Statement: [Scoops Ahoy, hasMenuBoard, flavor list]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMenuBoard Context triple: [Scoops Ahoy, hasMenuBoard, flavor list]
-
A.
hasServiceBoard
Indicates that an entity is associated with or connected to a specific service board, such as a panel or group responsible for providing or overseeing services.
-
B.
hasBoardType
Indicates that an entity is associated with or uses a specific type or category of board.
-
C.
hasVideoBoard
Indicates that an entity is equipped with or includes a video board (graphics/display hardware component).
-
D.
hasMenuItem
Indicates that one entity (typically a menu or menu section) includes or offers another entity as one of its menu items.
-
E.
mainBoardFor
Indicates that one entity serves as the primary circuit board or central board used by another entity.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633c2b1108190b492ca23487b91f8 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:38 p.m.