Triple
T35076063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parentesi lamp |
E1012310
|
entity |
| Predicate | floorBaseType |
P182082
|
FINISHED |
| Object | weighted base or floor fixing |
—
|
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: weighted base or floor fixing | Statement: [Parentesi lamp, floorBaseType, weighted base or floor fixing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: floorBaseType Context triple: [Parentesi lamp, floorBaseType, weighted base or floor fixing]
-
A.
floorLevelType
Indicates the classification or type of a floor level within a building (e.g., basement, ground, mezzanine, upper floor).
-
B.
floorType
Indicates the type or material classification of a floor associated with an entity.
-
C.
floorBelow
Indicates that one entity is located on the floor directly beneath another entity within the same structure.
-
D.
foundationType
Indicates the structural or organizational basis on which something is built, established, or supported.
-
E.
floorContext
Indicates the specific floor or level within a building or structure that serves as the contextual setting for an event, object, or relationship.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7865b4684819093f95e659522b75e |
completed | May 3, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f78575917481909a3defd6a4c366bd |
completed | May 3, 2026, 5:27 p.m. |
Created at: May 3, 2026, 4:01 p.m.