Triple
T29323813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bubblegum Alley |
E743585
|
entity |
| Predicate | wallCoverage |
P6896
|
FINISHED |
| Object | thousands of pieces of gum |
—
|
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: thousands of pieces of gum | Statement: [Bubblegum Alley, wallCoverage, thousands of pieces of gum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wallCoverage Context triple: [Bubblegum Alley, wallCoverage, thousands of pieces of gum]
-
A.
wallCharacteristic
Indicates that a specified characteristic or property is attributed to a wall.
-
B.
wallMaterial
Indicates that one entity is the material from which a wall or walls of another entity are constructed.
-
C.
wallTreatment
chosen
Indicates how a wall is finished, covered, or treated in terms of its surface appearance or protective coating.
-
D.
hasOutfieldWallCovering
Indicates that an outfield wall is covered or surfaced with a particular material or type of covering.
-
E.
wallFeature
Indicates that one entity functions as a structural or design feature associated with a wall of 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6689407bc8190b801c02fcb6e0e9a |
completed | May 2, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:25 p.m.