Triple
T29030145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Accredited Standards Committee X3 |
E737704
|
entity |
| Predicate | notableStandardSeries |
P203772
|
FINISHED |
| Object | ANSI X3.135 SQL |
E1563541
|
NE 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: ANSI X3.135 SQL | Statement: [Accredited Standards Committee X3, notableStandardSeries, ANSI X3.135 SQL]
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 (5 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a01f4d954e08190aff3756955212d67 |
completed | May 11, 2026, 3:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2505d780d88190a0ed521fd29d0883 |
completed | June 7, 2026, 5:47 a.m. |
| PD | Predicate disambiguation | batch_6a01edadb9248190be592287530740a5 |
completed | May 11, 2026, 2:54 p.m. |
| PDg | Predicate description generation | batch_6a01f4d84fa08190be6dea78f3fa9d8c |
completed | May 11, 2026, 3:25 p.m. |
Created at: April 28, 2026, 9:54 a.m.