Triple
T28361816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KNYL |
E718380
|
entity |
| Predicate | supportsTrainingOperations |
P42205
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [KNYL, supportsTrainingOperations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTrainingOperations Context triple: [KNYL, supportsTrainingOperations, yes]
-
A.
supportsOperationsIn
Indicates that one entity enables, facilitates, or backs the execution of operations within a specified context, area, or domain of another entity.
-
B.
supportsLinkTraining
Indicates that one entity is capable of assisting or enabling another entity in performing link training for a communication or data connection.
-
C.
supportsOperationsWith
Indicates that one entity enables, facilitates, or is compatible with the execution of operations involving another entity.
-
D.
trainingSupport
chosen
Indicates that one entity provides assistance, resources, or facilitation to help another entity conduct or participate in training activities.
-
E.
providesTrainingFor
Indicates that one entity delivers or conducts training activities intended to develop the skills or knowledge of another entity.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_6a008d6085508190a71c52cd028a6297 |
completed | May 10, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_6a008ced31448190b8fc60bf87b40647 |
completed | May 10, 2026, 1:49 p.m. |
Created at: April 28, 2026, 12:52 a.m.