Triple
T11321012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BOLT |
E268092
|
entity |
| Predicate | hasClientInterface |
P12981
|
FINISHED |
| Object | trading terminals |
—
|
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: trading terminals | Statement: [BOLT, hasClientInterface, trading terminals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClientInterface Context triple: [BOLT, hasClientInterface, trading terminals]
-
A.
hasClient
Indicates that an entity maintains a client relationship with another entity, typically as a provider of goods or services.
-
B.
hasInterface
chosen
Indicates that one entity provides, exposes, or is connected through a defined interface to another entity.
-
C.
hasMinimalInterface
Indicates that one entity provides only the smallest necessary set of methods, features, or interaction points required for another entity to use or interact with it.
-
D.
hasCommandLineInterface
Indicates that an entity provides or supports interaction through a command-line interface (CLI).
-
E.
hasCommunicationInterface
Indicates that one entity provides or supports a specific means or channel through which it can communicate or exchange data with another entity or system.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9dff37081909622623e66e17ccd |
completed | April 9, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69d787ad575081908274280bf75d95fd |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.