Triple
T34395344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elite Plus |
E882813
|
entity |
| Predicate | statusMaintenance |
P71131
|
FINISHED |
| Object | requires requalification |
—
|
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: requires requalification | Statement: [Elite Plus, statusMaintenance, requires requalification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusMaintenance Context triple: [Elite Plus, statusMaintenance, requires requalification]
-
A.
maintenanceStatus
Indicates the current state or condition of an entity with respect to its maintenance activities, such as whether it is pending, in progress, completed, or overdue.
-
B.
maintenance
Indicates that an entity performs, requires, or is involved in upkeep, repair, or preservation activities for another entity or system.
-
C.
hasMaintenance
chosen
Indicates that an entity is subject to, associated with, or requires a particular maintenance activity or maintenance record.
-
D.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
-
E.
statusInterface
Indicates that an entity serves as, or is associated with, an interface that reports or reflects its current status.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff53389a0481908b2baeb43c6294f0 |
completed | May 9, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69ff52e2b4b88190b38d160d771fe14b |
completed | May 9, 2026, 3:29 p.m. |
Created at: May 1, 2026, 1:59 a.m.