Triple
T37872438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of the Jade Serpent |
E944638
|
entity |
| Predicate | minLevelAtRelease |
P65817
|
FINISHED |
| Object | 85 |
—
|
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: 85 | Statement: [Temple of the Jade Serpent, minLevelAtRelease, 85]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minLevelAtRelease Context triple: [Temple of the Jade Serpent, minLevelAtRelease, 85]
-
A.
minimumLevel
chosen
Indicates that one entity specifies the lowest allowable or required level, degree, or threshold at which another entity, condition, or action becomes valid or applicable.
-
B.
initialReleaseFor
Indicates that one entity is the first or original release version associated with another entity (such as a work, product, or edition).
-
C.
recommendedLevelAtLaunch
Indicates the level that is advised or expected for an entity at the moment it is first introduced or made available.
-
D.
initialReleaseWith
Indicates that two or more entities were first released together as part of the same initial release event or package.
-
E.
modificationLevel
Indicates the degree or extent to which something has been altered, adjusted, or changed from its original state.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.