Triple
T36704193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potts glass |
E906309
|
entity |
| Predicate | hasLatticeVersions |
P200928
|
FINISHED |
| Object | finite-dimensional Potts glass |
—
|
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: finite-dimensional Potts glass | Statement: [Potts glass, hasLatticeVersions, finite-dimensional Potts glass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLatticeVersions Context triple: [Potts glass, hasLatticeVersions, finite-dimensional Potts glass]
-
A.
hasLiveVersions
Indicates that an entity has one or more recorded or documented live-performance versions of itself.
-
B.
hasMultipleVersions
Indicates that an entity exists in more than one distinct version or revision.
-
C.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
D.
hasVersionFor
Indicates that one entity serves as a specific version or variant tailored for another entity.
-
E.
hasVersionStatus
Indicates that an entity is associated with a particular version state or status within its lifecycle or revision history.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69ffb97ae1508190bf3addd6e2aac281 |
completed | May 9, 2026, 10:47 p.m. |
Created at: May 3, 2026, 4:12 p.m.