Triple
T24848117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asteroid B-612 |
E621811
|
entity |
| Predicate | maintenanceRoutine |
P59741
|
FINISHED |
| Object | daily cleaning of volcanoes |
—
|
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: daily cleaning of volcanoes | Statement: [Asteroid B-612, maintenanceRoutine, daily cleaning of volcanoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintenanceRoutine Context triple: [Asteroid B-612, maintenanceRoutine, daily cleaning of volcanoes]
-
A.
maintenancePractice
Indicates the specific actions or methods used to preserve, repair, or optimize the condition or performance of something over time.
-
B.
maintenance
Indicates that an entity performs, requires, or is involved in upkeep, repair, or preservation activities for another entity or system.
-
C.
maintenanceEvent
Indicates that a maintenance-related action or occurrence takes place involving one or more entities.
-
D.
maintenanceType
Indicates the specific category or kind of maintenance activity associated with an entity or relationship.
-
E.
maintenanceCycle
chosen
Indicates the recurring schedule or interval at which maintenance activities are performed or required.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:20 a.m.