Triple
T4402464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X.25 |
E93647
|
entity |
| Predicate | definesInterfaceBetween |
P12981
|
FINISHED |
| Object | data terminal equipment |
—
|
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: data terminal equipment | Statement: [X.25, definesInterfaceBetween, data terminal equipment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesInterfaceBetween Context triple: [X.25, definesInterfaceBetween, data terminal equipment]
-
A.
usesInterface
Indicates that one entity interacts with or operates another entity through a specified interface or set of interface methods.
-
B.
isImplementationOf
Indicates that one entity realizes, fulfills, or concretely carries out the specification, interface, or abstract definition provided by another entity.
-
C.
hasInterface
chosen
Indicates that one entity provides, exposes, or is connected through a defined interface to another entity.
-
D.
usedInInterface
Indicates that something is employed or incorporated as a component or element within a user interface.
-
E.
definedVia
Indicates that one entity is specified, characterized, or given its meaning by reference to another entity or construct.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b352d08a0c8190ac6c125df40eca75 |
completed | March 12, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69b34f597998819092477efdedb51427 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:28 p.m.