Triple
T26765637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eightfold Way |
E674928
|
entity |
| Predicate | groupHadronsBy |
P155067
|
FINISHED |
| Object | representation of SU(3) |
—
|
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: representation of SU(3) | Statement: [Eightfold Way, groupHadronsBy, representation of SU(3)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groupHadronsBy Context triple: [Eightfold Way, groupHadronsBy, representation of SU(3)]
-
A.
groupedInto
Indicates that multiple entities are collected or organized together as members of a common group or category.
-
B.
byGroup
chosen
Indicates that something is organized, classified, or associated according to a particular group or grouping.
-
C.
movementGrouping
Indicates that multiple movements or motion events are treated as a single grouped or coordinated unit within a larger action or process.
-
D.
groupingRule
Indicates a rule or criterion that defines how multiple entities are grouped or clustered together based on shared characteristics or conditions.
-
E.
allyGroup
Indicates that two or more entities belong to the same allied group or faction, cooperating or aligned in purpose or interests.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 3:59 a.m.