Triple
T16825431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISDN |
E409006
|
entity |
| Predicate | PRIConfiguration |
P124988
|
FINISHED |
| Object | 23B+D in North America and Japan |
—
|
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: 23B+D in North America and Japan | Statement: [ISDN, PRIConfiguration, 23B+D in North America and Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PRIConfiguration Context triple: [ISDN, PRIConfiguration, 23B+D in North America and Japan]
-
A.
portConfiguration
Indicates how ports are arranged, assigned, or set up for use within a system or device.
-
B.
configuration
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
-
C.
laterConfiguration
Indicates that one configuration occurs after another in time, representing a subsequent or later state relative to a prior configuration.
-
D.
pumpConfiguration
Indicates the specific setup or arrangement in which a pump operates or is installed, including its components, settings, and connections.
-
E.
primaryMirrorConfiguration
Indicates the specific structural and optical setup used for a system’s primary mirror.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:23 a.m.