Triple
T16825429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISDN |
E409006
|
entity |
| Predicate | BRIConfiguration |
P2093
|
FINISHED |
| Object | 2B+D |
—
|
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: 2B+D | Statement: [ISDN, BRIConfiguration, 2B+D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BRIConfiguration Context triple: [ISDN, BRIConfiguration, 2B+D]
-
A.
brakeConfigurationSupport
Indicates that one entity provides or defines support for the brake configuration of another entity.
-
B.
configuration
chosen
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
-
C.
configurationProtocol
Indicates the protocol or method used to configure or set up a system, device, or component.
-
D.
numberOfConfigurations
Indicates the total count of distinct configurations associated with or applicable to a given entity or situation.
-
E.
configurationVia
Indicates that one entity is set up, customized, or controlled through another entity serving as its configuration mechanism or source.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b3126db88190ac5595b0d50e4232 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.