Triple
T20128118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 826 Valencia |
E490810
|
entity |
| Predicate | hasStorefrontTheme |
P61999
|
FINISHED |
| Object | pirate supply store |
—
|
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: pirate supply store | Statement: [826 Valencia, hasStorefrontTheme, pirate supply store]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStorefrontTheme Context triple: [826 Valencia, hasStorefrontTheme, pirate supply store]
-
A.
hasThemeType
Indicates that something is associated with or characterized by a particular thematic category or type.
-
B.
hasThemeConnection
Indicates a relationship where one entity is linked to another through a shared or related theme, topic, or conceptual focus.
-
C.
hasThemingDetail
chosen
Indicates that something includes or is associated with a specific thematic element, motif, or stylistic detail.
-
D.
supportsThemingSystem
Indicates that an entity is compatible with and can operate using a theming system for customizable appearance or style.
-
E.
hasMotiveTheme
Indicates that an action, event, or situation is associated with a central motivating theme or underlying driving idea.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6675fe3d48190b0c20b483a951e68 |
completed | April 20, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:31 p.m.