Triple
T37471052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skoldus Hall |
E931152
|
entity |
| Predicate | availableSincePatch |
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: [Skoldus Hall, availableSincePatch, 9.0.1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableSincePatch Context triple: [Skoldus Hall, availableSincePatch, 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.
appliedSince
Indicates that a particular condition, rule, status, or action has been in effect starting from a specified point in time and continues from that date onward.
-
C.
supportsSinceVersion
Indicates that a given entity has provided support or compatibility for another entity starting from a specified version onward.
-
D.
introducedAfter
Indicates that one entity was introduced at a later time or stage than another entity.
-
E.
officialVersionSince
Indicates the point in time from which a particular version of something is recognized or treated as the official version.
- 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_69fb8e61d5a48190afc273af1fb54af9 |
completed | May 6, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0c53c08190b64291bac58cdb4c |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.