Triple
T27107721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandeliers |
E686624
|
entity |
| Predicate | installationRequirement |
P29759
|
FINISHED |
| Object | electrical wiring |
—
|
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: electrical wiring | Statement: [Chandeliers, installationRequirement, electrical wiring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: installationRequirement Context triple: [Chandeliers, installationRequirement, electrical wiring]
-
A.
requiresInstallation
chosen
Indicates that one entity must be installed or set up before the other can be used or become operational.
-
B.
installationFeature
Indicates that one entity serves as a feature, component, or functional element of another entity’s installation.
-
C.
platformRequirement
Indicates that one entity specifies a necessary platform or environment condition that must be met for another entity to function or be applicable.
-
D.
maintenanceRequirement
Indicates that an entity is obligated to perform, schedule, or adhere to specific maintenance activities or conditions for another entity or system.
-
E.
requiresSoftware
Indicates that one entity depends on specific software being present or installed in order to function, operate, or be used.
- 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_69ef148accd48190b6ed6e13a15f2a4f |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f625411c14819086492062e86ba8d5 |
completed | May 2, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 8:51 a.m.