Triple
T37464508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twinspell |
E930999
|
entity |
| Predicate | mechanicStatus |
P23573
|
FINISHED |
| Object | evergreenInWildOnly |
—
|
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: evergreenInWildOnly | Statement: [Twinspell, mechanicStatus, evergreenInWildOnly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanicStatus Context triple: [Twinspell, mechanicStatus, evergreenInWildOnly]
-
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.
associatedWithMechanic
chosen
Indicates a relationship where an entity is connected or linked to a mechanic, such as a process, rule, or functional mechanism involved in its operation or behavior.
-
C.
cargoConditionMechanic
Indicates that a mechanic assesses, maintains, or reports on the condition of cargo.
-
D.
mechanicRisk
Indicates that there is a potential danger, hazard, or adverse outcome associated with a particular mechanical process, operation, or mechanism.
-
E.
driverStatus
Indicates the current operational or availability state of a driver in relation to their driving duties.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:17 p.m.