Triple
T7296461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archie |
E164533
|
entity |
| Predicate | queryInterface |
P11686
|
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: [Archie, queryInterface, command-line interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: queryInterface Context triple: [Archie, queryInterface, command-line interface]
-
A.
usesInterface
chosen
Indicates that one entity interacts with or operates another entity through a specified interface or set of interface methods.
-
B.
dataInterface
Indicates that one entity serves as a data interface through which another entity can access, exchange, or manipulate data.
-
C.
languageOfInterface
Indicates the language used by or presented in a user interface.
-
D.
mountingInterface
Indicates that one entity serves as the surface, structure, or connection point onto which another entity is mounted or attached.
-
E.
interfaceLocation
Indicates the spatial or logical position where two systems, components, or entities meet and interact.
- 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb8e48d48190ada4d507f3b61bc4 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3 p.m.