Triple
T17560838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GIN index |
E427691
|
entity |
| Predicate | maintenanceOperation |
P42008
|
FINISHED |
| Object | VACUUM to clean up pending list |
—
|
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: VACUUM to clean up pending list | Statement: [GIN index, maintenanceOperation, VACUUM to clean up pending list]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintenanceOperation Context triple: [GIN index, maintenanceOperation, VACUUM to clean up pending list]
-
A.
maintenanceType
Indicates the specific category or kind of maintenance activity associated with an entity or relationship.
-
B.
maintenanceEvent
Indicates that a maintenance-related action or occurrence takes place involving one or more entities.
-
C.
maintenance
Indicates that an entity performs, requires, or is involved in upkeep, repair, or preservation activities for another entity or system.
-
D.
maintenancePractice
chosen
Indicates the specific actions or methods used to preserve, repair, or optimize the condition or performance of something over time.
-
E.
maintenanceNote
Indicates that there is a note or comment documenting information, instructions, or observations related to the maintenance of an entity.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e456267e208190a1238fbe1a535bb0 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.