Triple
T18632858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Series 7 chair |
E455464
|
entity |
| Predicate | stackingCapacity |
P100802
|
FINISHED |
| Object | up to 12 chairs (approximate) |
—
|
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: up to 12 chairs (approximate) | Statement: [Series 7 chair, stackingCapacity, up to 12 chairs (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stackingCapacity Context triple: [Series 7 chair, stackingCapacity, up to 12 chairs (approximate)]
-
A.
storageCapacity
Indicates the maximum amount of data or material that a storage entity can hold.
-
B.
dataCapacity
Indicates the maximum amount of data that something can store, handle, or transmit.
-
C.
stackable
chosen
Indicates that one entity can be placed on top of another in a stable, orderly manner, typically allowing multiple such entities to be arranged vertically.
-
D.
stacking
Indicates that one entity is placed directly on top of another, forming a vertical arrangement or pile.
-
E.
ramCapacity
Indicates the amount of system memory (RAM) that an entity possesses or supports.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54fc5c7ec8190ab0c64f009583f96 |
completed | April 19, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69e478d4a7948190a4bb9223bb5dddfc |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.