Triple
T17752870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dyson index β |
E443154
|
entity |
| Predicate | value2CorrespondsTo |
P106119
|
FINISHED |
| Object | unitary symmetry |
—
|
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: unitary symmetry | Statement: [Dyson index β, value2CorrespondsTo, unitary symmetry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: value2CorrespondsTo Context triple: [Dyson index β, value2CorrespondsTo, unitary symmetry]
-
A.
vertexCorrespondsTo
Indicates that one vertex is associated with, or represents the same conceptual point as, another vertex in a corresponding structure or context.
-
B.
correspondsWith
chosen
Indicates that two entities are in mutual alignment or agreement, such that one matches, parallels, or is equivalent to the other in a specified respect.
-
C.
containsCorrespondenceWith
Indicates that one entity includes or holds correspondence (such as messages or communications) that is associated with or exchanged with another entity.
-
D.
valueDefinedBy
Indicates that the value of one entity is determined, specified, or constrained by another entity.
-
E.
valueRelation
Indicates a comparative or associative relationship between the values or magnitudes of two or more entities.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4841c0540819093a32d759775c61f |
completed | April 19, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:10 a.m.