Triple
T37541651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Path of Ascension |
E933338
|
entity |
| Predicate | updateStatus |
P188714
|
FINISHED |
| Object | introduced in patch 9.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: introduced in patch 9.0 | Statement: [Path of Ascension, updateStatus, introduced in patch 9.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updateStatus Context triple: [Path of Ascension, updateStatus, introduced in patch 9.0]
-
A.
upgradeStatus
Indicates the current state or progress of an upgrade process applied to an entity.
-
B.
statusChange
Indicates a transition in an entity’s state or condition from one status to another over time.
-
C.
exportStatus
Indicates the current state or outcome of an entity’s export process (e.g., pending, in progress, completed, or failed).
-
D.
updateProcess
Indicates the action or procedure by which an existing item, system, or state is modified to a newer or revised version.
-
E.
customStatus
Indicates that an entity has a user-defined or non-standard status assigned to it.
- F. None of above. chosen
Provenance (4 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_69f76ec999288190ae26ec7b6aea7046 |
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. |
| PDg | Predicate description generation | batch_69fbacaea12c8190a4c99e64335f0e7e |
completed | May 6, 2026, 9:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.