Triple
T7600647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | baryon decuplet |
E179972
|
entity |
| Predicate | hasRepresentationDimension |
P77171
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [baryon decuplet, hasRepresentationDimension, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRepresentationDimension Context triple: [baryon decuplet, hasRepresentationDimension, 10]
-
A.
hasDimensionality
Indicates that an entity possesses a specific number of dimensions or a particular dimensional structure.
-
B.
hasDimension
Indicates that an entity possesses a specific measurable extent or size along one or more axes (e.g., length, width, height).
-
C.
hasIrreducibleRepresentationOfDimension
chosen
Indicates that an entity possesses an irreducible representation whose vector space has the specified dimension.
-
D.
hasIndividualDimension
Indicates that an entity possesses a specific, separately identifiable dimension or measurable extent as an individual attribute.
-
E.
dimensionCount
Indicates the number of distinct dimensions or axes associated with an entity or data structure.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d9c55c8190841f3bf3225c096a |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.