Triple
T18952540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Room for one colour |
E463688
|
entity |
| Predicate | hasInstallationElement |
P133927
|
FINISHED |
| Object | monofrequency lamps |
—
|
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: monofrequency lamps | Statement: [Room for one colour, hasInstallationElement, monofrequency lamps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInstallationElement Context triple: [Room for one colour, hasInstallationElement, monofrequency lamps]
-
A.
hasParentInstallation
Indicates that one installation is the parent or higher-level installation to which another installation belongs or from which it is derived.
-
B.
hasMajorInstallation
Indicates that one entity possesses, hosts, or contains a primary or significant facility, base, or installation of another entity.
-
C.
requiresInstallation
Indicates that one entity must be installed or set up before the other can be used or become operational.
-
D.
typeOfInstallationSupported
Indicates that one entity supports or is compatible with a specified type or method of installation for another entity.
-
E.
installedAt
Indicates that something has been set up, placed, or put into operation at a specific location or site.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d544fef8819091147189ddd89617 |
completed | April 20, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, noon