Triple
T15380785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morinomiya Depot |
E367791
|
entity |
| Predicate | maintenanceType |
P118531
|
FINISHED |
| Object | light maintenance |
—
|
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: light maintenance | Statement: [Morinomiya Depot, maintenanceType, light maintenance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintenanceType Context triple: [Morinomiya Depot, maintenanceType, light maintenance]
-
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.
maintenanceFeature
Indicates that one entity serves as a maintenance-related feature, capability, or component associated with another entity.
-
D.
maintenanceConcept
Indicates a conceptual or abstract relationship related to maintenance activities, strategies, or principles rather than a specific maintenance event.
-
E.
maintenanceCycle
Indicates the recurring schedule or interval at which maintenance activities are performed or required.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e61928c81908852c355d537ed9c |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:19 a.m.