Triple
T38567863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gelfand–Tsetlin graph |
E928276
|
entity |
| Predicate | hasLevel0Vertex |
P4584
|
FINISHED |
| Object | empty signature at level 0 |
—
|
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: empty signature at level 0 | Statement: [Gelfand–Tsetlin graph, hasLevel0Vertex, empty signature at level 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLevel0Vertex Context triple: [Gelfand–Tsetlin graph, hasLevel0Vertex, empty signature at level 0]
-
A.
hasZeroPosition
Indicates that an entity occupies or is assigned to the reference (zero) position within a defined coordinate system or ordered structure.
-
B.
hasVertex
chosen
Indicates that an object, typically a geometric shape or graph, includes a specified vertex as one of its corner or node points.
-
C.
hasAtomAtZero
Indicates that an entity has an atom located at the zero position or origin in its defined coordinate or index system.
-
D.
hasZeroStructure
Indicates that an entity lacks any internal components, subparts, or structural organization.
-
E.
hasLevelNumber
Indicates that an entity is associated with a specific level identified by a numerical value.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
Created at: May 3, 2026, 4:32 p.m.