Triple
T15417656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Subwoofer |
E369283
|
entity |
| Predicate | typicallyPlaced |
P91034
|
FINISHED |
| Object | On floor |
—
|
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: On floor | Statement: [Big Subwoofer, typicallyPlaced, On floor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyPlaced Context triple: [Big Subwoofer, typicallyPlaced, On floor]
-
A.
oftenLocatedAt
chosen
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
-
B.
typicalStorePlacement
Indicates the usual or standard physical location where an item is placed or displayed within a store.
-
C.
typicalDecorationPlacement
Indicates the usual or most common spatial arrangement where a decoration is placed relative to another object or environment.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
typicalUseLocation
Indicates the usual or most common location where an entity is used or operates.
- 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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ea8a8a081909749db1b29d85fcc |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.