Triple
T11542275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icecrown Citadel |
E273700
|
entity |
| Predicate | introducedInPatch |
P99620
|
FINISHED |
| Object | Patch 3.3.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: Patch 3.3.0 | Statement: [Icecrown Citadel, introducedInPatch, Patch 3.3.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedInPatch Context triple: [Icecrown Citadel, introducedInPatch, Patch 3.3.0]
-
A.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by another entity.
-
B.
introducedInProduct
Indicates that something (such as a feature, component, or concept) first appeared or was initially made available within a particular product.
-
C.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
D.
introducedAfter
Indicates that one entity was introduced at a later time or stage than another entity.
-
E.
introducedInTheme
Indicates that something (such as a concept, character, or element) is first presented or brought into use within a particular theme.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e09eec8190894069d86b79183d |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d8279925e4819089210611c0d8e61a |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 8, 2026, 9:37 p.m.