Triple
T4391002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theano |
E99360
|
entity |
| Predicate | maintenanceStatus |
P56340
|
FINISHED |
| Object | no new major features |
—
|
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: no new major features | Statement: [Theano, maintenanceStatus, no new major features]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintenanceStatus Context triple: [Theano, maintenanceStatus, no new major features]
-
A.
maintenance
Indicates that an entity performs, requires, or is involved in upkeep, repair, or preservation activities for another entity or system.
-
B.
continuityStatus
Indicates the state of whether something continues without interruption or has been broken, paused, or reset over time.
-
C.
automationStatus
Indicates whether a process, task, or system is being performed automatically or requires manual intervention.
-
D.
maintenanceFeature
Indicates that one entity serves as a maintenance-related feature, capability, or component associated with another entity.
-
E.
modernStatus
Indicates the current or contemporary condition, classification, or standing of an entity in the present time.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352843d7c8190929b94c94eaa63df |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3501834448190bedf775a80da4778 |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:19 p.m.