Triple
T17559381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Enqueue Service |
E427659
|
entity |
| Predicate | relevantFromVersion |
P13979
|
FINISHED |
| Object | Oracle 9i RAC and later |
—
|
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: Oracle 9i RAC and later | Statement: [Global Enqueue Service, relevantFromVersion, Oracle 9i RAC and later]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relevantFromVersion Context triple: [Global Enqueue Service, relevantFromVersion, Oracle 9i RAC and later]
-
A.
officialVersionSince
chosen
Indicates the point in time from which a particular version of something is recognized or treated as the official version.
-
B.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by another entity.
-
C.
basedOnVersion
Indicates that one entity is derived from, built upon, or created using a specific version of another entity as its basis.
-
D.
previousVersionIncluded
Indicates that an earlier version of an entity was contained within, or formed part of, the current entity.
-
E.
historicalVersion
Indicates that one entity represents an earlier or past version in the history or evolution of another entity.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4562573e48190a19f30fe915a5455 |
completed | April 19, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fb39948190a82a597c5bac5c57 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.