Triple
T21576224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ladder |
E532399
|
entity |
| Predicate | preferredMaterialForElectricalWork |
P144323
|
FINISHED |
| Object | fiberglass |
—
|
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: fiberglass | Statement: [ladder, preferredMaterialForElectricalWork, fiberglass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preferredMaterialForElectricalWork Context triple: [ladder, preferredMaterialForElectricalWork, fiberglass]
-
A.
typeOfElectricity
Indicates that one entity specifies the particular kind or category of electricity associated with another entity.
-
B.
suppliedMaterialType
Indicates the type or category of material that is provided or supplied in a given context.
-
C.
hasElectricalProperty
Indicates that an entity possesses a specific electrical characteristic or behavior, such as conductivity, resistance, or charge-related properties.
-
D.
electricalPower
Indicates that one entity supplies, carries, or is associated with electrical power to or for another entity.
-
E.
materialUsed
Indicates that one entity is made from, incorporates, or utilizes the other entity as its material or substance.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9d07ddc8190a4bba08223e56f46 |
completed | April 27, 2026, 4:45 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:31 p.m.