Triple
T28296295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COMMAND.COM |
E713579
|
entity |
| Predicate | internalCommand |
P136972
|
FINISHED |
| Object | DIR |
—
|
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: DIR | Statement: [COMMAND.COM, internalCommand, DIR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internalCommand Context triple: [COMMAND.COM, internalCommand, DIR]
-
A.
coreCommand
Indicates that one entity serves as the primary or central command or control authority over another entity or process.
-
B.
centralCommand
Indicates that one entity serves as the primary controlling or coordinating authority over the operations, decisions, or activities of another entity or group.
-
C.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
D.
commandsIn
chosen
Indicates that one entity contains, defines, or includes the set of commands that are available or applicable within another entity.
-
E.
associatedCommand
Indicates a relationship where one entity is linked to, or meant to be used with, a particular command or set of commands.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 27, 2026, 11:32 p.m.