Triple
T37472250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halls of Atonement |
E931181
|
entity |
| Predicate | levelRangeAtRelease |
P100052
|
FINISHED |
| Object | 50-60 |
—
|
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: 50-60 | Statement: [Halls of Atonement, levelRangeAtRelease, 50-60]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: levelRangeAtRelease Context triple: [Halls of Atonement, levelRangeAtRelease, 50-60]
-
A.
zoneLevelRangeAtLaunch
chosen
Indicates the range of zone levels that apply at the moment something is launched or begins.
-
B.
recommendedLevelAtLaunch
Indicates the level that is advised or expected for an entity at the moment it is first introduced or made available.
-
C.
volumeReleased
Indicates that a specific volume (such as a book, issue, or installment) has been officially released or made publicly available.
-
D.
liveVersionReleasedOn
Indicates the date or time when a live version of something (such as a product, feature, or content) is officially released or made available.
-
E.
stableReleaseYear
Indicates the calendar year in which a stable, non-beta version of something (such as software or a product) was officially released.
- 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.