Triple
T37471176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mort'regar |
E931155
|
entity |
| Predicate | availableInPatch |
P99620
|
FINISHED |
| Object | 9.0.1 |
—
|
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: 9.0.1 | Statement: [Mort'regar, availableInPatch, 9.0.1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableInPatch Context triple: [Mort'regar, availableInPatch, 9.0.1]
-
A.
introducedInPatch
chosen
Indicates that something (such as a feature, change, or fix) first appeared or became available in a specific software patch.
-
B.
patchAvailable
Indicates that an update or fix has been released and is available to be applied to the referenced software or system.
-
C.
alsoAvailableInVersion
Indicates that the same item, feature, or content is offered in another specified version or edition.
-
D.
reintroducedInPatch
Indicates that something previously removed or absent was added back or made available again as part of a specific software patch or update.
-
E.
mayBeAvailableIn
Indicates that an entity has the potential to be obtainable, accessible, or present within a specified context, location, or medium.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.