Triple
T15535257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mushroom Bridge |
E370322
|
entity |
| Predicate | hasBillboards |
P5950
|
FINISHED |
| Object | Mushroom Kingdom-themed advertisements |
—
|
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: Mushroom Kingdom-themed advertisements | Statement: [Mushroom Bridge, hasBillboards, Mushroom Kingdom-themed advertisements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBillboards Context triple: [Mushroom Bridge, hasBillboards, Mushroom Kingdom-themed advertisements]
-
A.
hasSignageIn
Indicates that appropriate signs or signage for an entity are present or installed within a specified location or area.
-
B.
hasSignage
chosen
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated entity.
-
C.
hasBillboardStar
Indicates that an entity has been awarded or features a star on a billboard, signifying recognition or promotion.
-
D.
hasSignageType
Indicates the specific category or kind of signage associated with an object, location, or entity.
-
E.
hasNeonSigns
Indicates that an entity features or is adorned with neon signs as part of its visual or advertising elements.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442e327c8190b4b879c8a3cd38e3 |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.