Triple
T970542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tesla Solar Roof |
E20933
|
entity |
| Predicate | installationMethod |
P17153
|
FINISHED |
| Object | full roof replacement |
—
|
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: full roof replacement | Statement: [Tesla Solar Roof, installationMethod, full roof replacement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: installationMethod Context triple: [Tesla Solar Roof, installationMethod, full roof replacement]
-
A.
installedBy
Indicates that one entity was set up, put in place, or made operational through the actions or intervention of another entity.
-
B.
installedAt
Indicates that something has been set up, placed, or put into operation at a specific location or site.
-
C.
installationCompleted
Indicates that the process of installing something has finished successfully.
-
D.
typeOfInstallation
chosen
Indicates the specific kind or category of installation associated with an entity (e.g., how or in what form something is installed).
-
E.
sisterInstallation
Indicates that two installations are related as counterparts or peers, typically within the same organization or system, without one being subordinate to the other.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b4497d688190b59c3a195e377080 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a6aa2c8190aebba71320ab678f |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.