Triple
T1580349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eightfold Way classification |
E33748
|
entity |
| Predicate | groupsIntoMultiplets |
P5709
|
FINISHED |
| Object | octets |
—
|
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: octets | Statement: [Eightfold Way classification, groupsIntoMultiplets, octets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groupsIntoMultiplets Context triple: [Eightfold Way classification, groupsIntoMultiplets, octets]
-
A.
numberOfGroups
Indicates the total count of distinct groups associated with or formed within a given context or entity.
-
B.
coveredGroup
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
-
C.
joinedPluralityBy
Indicates that multiple entities collectively became members or participants of the same group, organization, or event through a shared act of joining.
-
D.
organizesInto
chosen
Indicates that one entity arranges, structures, or groups another entity into a particular order, system, or set of categories.
-
E.
separatedInto
Indicates that something has been divided or split into distinct parts, groups, or components.
- 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_69a885f27a4c8190a4622252cdf54c00 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abacfb1144819080c5687175aba1e1 |
completed | March 7, 2026, 4:43 a.m. |
| PD | Predicate disambiguation | batch_69aa61b0f5bc8190b1dc272990a59c13 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:27 p.m.