Triple
T12516082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M4 macro processor |
E299193
|
entity |
| Predicate | hasCommandName |
P15534
|
FINISHED |
| Object | m4 |
—
|
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: m4 | Statement: [M4 macro processor, hasCommandName, m4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommandName Context triple: [M4 macro processor, hasCommandName, m4]
-
A.
hasCommand
chosen
Indicates that one entity possesses, controls, or is associated with a specific command or directive applied to another entity or process.
-
B.
containsCommand
Indicates that one entity includes or embeds a command directed at or executable by another entity.
-
C.
hasComponentCommand
Indicates that an entity includes or controls another entity as a subordinate or component command within an organizational or command structure.
-
D.
hasCommandSystem
Indicates that one entity possesses, uses, or is associated with a particular command or control system.
-
E.
hasCommandResponsibilityFor
Indicates that one entity holds authoritative control over, and is responsible for directing and overseeing, the actions or operations 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.