Triple
T815547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unix shell |
E17645
|
entity |
| Predicate | primaryInterfaceType |
P5099
|
FINISHED |
| Object | command-line interface |
—
|
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: command-line interface | Statement: [Unix shell, primaryInterfaceType, command-line interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryInterfaceType Context triple: [Unix shell, primaryInterfaceType, command-line interface]
-
A.
primaryInterface
chosen
Indicates that one entity serves as the main or default interface through which another entity is accessed or interacted with.
-
B.
primaryMode
Indicates the main or most commonly used method, manner, or form in which an action, process, or interaction is carried out between entities.
-
C.
primaryTargetType
Indicates the main category or type of entity that is the principal focus or intended recipient of an action, effect, or operation.
-
D.
primaryDeviceCategory
Indicates the main type or class of device associated with an entity or event, distinguishing it from other possible device categories.
-
E.
primaryService
Indicates that one entity serves as the main or principal service provided or used in relation to 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab5157b08190b6c8f2fd455f261e |
completed | March 1, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69a4aa756920819080ae82948974c876 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.