Triple
T29030145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Accredited Standards Committee X3 |
E737704
|
entity |
| Predicate | notableStandardSeries |
—
|
GENERATED |
| Object | ANSI X3.135 SQL |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStandardSeries Context triple: [Accredited Standards Committee X3, notableStandardSeries, ANSI X3.135 SQL]
-
A.
notableStandard
Indicates that one entity is a widely recognized or influential standard that the other entity is associated with or exemplifies.
-
B.
notableSeries
Indicates that an entity is a significant or well-known installment within a particular series or franchise.
-
C.
notableOriginalSeries
Indicates that an entity is recognized as a significant or distinguished original series associated with another entity (such as a platform, creator, or franchise).
-
D.
notableSeriesStyle
Indicates that a work is created in the characteristic style of a notable series or franchise.
-
E.
notableWorkSeries
Indicates that a work is part of a series for which the subject is notably known or recognized.
- F. None of above. chosen
Provenance (1 batch)
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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
Created at: April 28, 2026, 9:54 a.m.