Triple
T26990425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type Commands |
E679848
|
entity |
| Predicate | typicalFunctionsInclude |
P42790
|
FINISHED |
| Object | setting training standards for assigned units |
—
|
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: setting training standards for assigned units | Statement: [Type Commands, typicalFunctionsInclude, setting training standards for assigned units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFunctionsInclude Context triple: [Type Commands, typicalFunctionsInclude, setting training standards for assigned units]
-
A.
typicalFunction
chosen
Indicates that something serves as the usual or characteristic function or role of an entity.
-
B.
typicalFunctionClass
Indicates that something belongs to the usual or characteristic functional category associated with it.
-
C.
typicalInvocations
Indicates the usual or most common ways in which an action, function, or process is called, used, or carried out.
-
D.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
E.
typicalInterface
Indicates that one entity serves as the standard or commonly used interface through which another entity is accessed or interacted with.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: April 27, 2026, 6:51 a.m.