Triple
T10763779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Structural Pattern Matching |
E253899
|
entity |
| Predicate | availableFromVersion |
P11235
|
FINISHED |
| Object | 3.10 |
—
|
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: 3.10 | Statement: [Structural Pattern Matching, availableFromVersion, 3.10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableFromVersion Context triple: [Structural Pattern Matching, availableFromVersion, 3.10]
-
A.
alsoAvailableInVersion
Indicates that the same item, feature, or content is offered in another specified version or edition.
-
B.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by another entity.
-
C.
officialVersionSince
Indicates the point in time from which a particular version of something is recognized or treated as the official version.
-
D.
usedInVersionRange
Indicates that something is applicable, valid, or in effect only within a specified range of versions.
-
E.
introducedWithVersion
chosen
Indicates that something first became available or was added starting from a specific version.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d731a504948190943f0e27c0d891ed |
completed | April 9, 2026, 4:57 a.m. |
| PD | Predicate disambiguation | batch_69d6f311529c819080ca5493d55d6050 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:16 p.m.