Triple
T29866679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | glTF |
E758479
|
entity |
| Predicate | introducedPBRInVersion |
P181744
|
FINISHED |
| Object | 2.0 |
—
|
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: 2.0 | Statement: [glTF, introducedPBRInVersion, 2.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedPBRInVersion Context triple: [glTF, introducedPBRInVersion, 2.0]
-
A.
introducedVersionOf
chosen
Indicates that one entity is the version in which another entity was first introduced or made available.
-
B.
introducedInProduct
Indicates that something (such as a feature, component, or concept) first appeared or was initially made available within a particular product.
-
C.
introducedInPatch
Indicates that something (such as a feature, change, or fix) first appeared or became available in a specific software patch.
-
D.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by another entity.
-
E.
improvedVersionIntroducedInYear
Indicates that a newer or enhanced version of something was first introduced or became available in a specified year.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 29, 2026, 5:51 p.m.