Triple
T15084898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tabouret Berger |
E360246
|
entity |
| Predicate | isBackless |
P117244
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tabouret Berger, isBackless, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBackless Context triple: [Tabouret Berger, isBackless, true]
-
A.
hasBackrest
Indicates that one entity (typically a seat or seating object) includes or is equipped with a supporting backrest.
-
B.
hasBackrestType
Indicates the specific kind or style of backrest that an object (typically a seat or chair) possesses.
-
C.
notWornWith
Indicates that one item is not worn at the same time as another item, implying mutual exclusivity in being worn together.
-
D.
hasStrapType
Indicates that an item is associated with or equipped with a specific type or style of strap.
-
E.
frontDesignSameAsBack
Indicates that the design on the front side of an object is identical to the design on its back side.
- F. None of above. chosen
Provenance (4 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00275cfa88190a13fe20b585d9fcb |
completed | April 15, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:03 a.m.