Triple
T37872439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of the Jade Serpent |
E944638
|
entity |
| Predicate | minLevelPostSquish |
P65817
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Temple of the Jade Serpent, minLevelPostSquish, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minLevelPostSquish Context triple: [Temple of the Jade Serpent, minLevelPostSquish, 10]
-
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.
minimumSize
Indicates that there is a lower bound or smallest allowable value for the size of something in the relationship.
-
C.
minimumAbove
Indicates that one value is the smallest among a set that is strictly greater than a given reference value.
-
D.
trimLevelBelow
Indicates that one entity’s trim level is lower or less equipped than another entity’s trim level.
-
E.
minimumMass
Indicates the smallest mass value that an entity or system is required, allowed, or observed to have within a given context.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.