Triple
T7663749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OAI-PMH |
E173573
|
entity |
| Predicate | currentStableVersion |
P13927
|
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: [OAI-PMH, currentStableVersion, 2.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentStableVersion Context triple: [OAI-PMH, currentStableVersion, 2.0]
-
A.
latestVersion
Indicates that one entity is the most recent or up-to-date version of another entity within a sequence or set of versions.
-
B.
latestMinorVersion
Indicates that one version is the most recent minor (non-major) update within the series of versions derived from another version.
-
C.
currentVersionAdopted
chosen
Indicates that a specified version is the one presently in use or officially adopted by the relevant entity or system.
-
D.
currentVersionDefinedIn
Indicates that the current or active version of an entity is specified or established within a particular source, document, or context.
-
E.
exportVersion
Indicates the specific release or revision identifier of an item as it is prepared for or used in export.
- 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_69c69955517c819085bc715b96d304d2 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7063dab1881909598b04999b8b690 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015f7430819099d3ea2781b7cee2 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 3:59 p.m.