Triple
T21277641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SO(n) |
E524430
|
entity |
| Predicate | hasTwoComponentsIn |
P48977
|
FINISHED |
| Object | O(n) with O(n) = SO(n) ⊔ (reflection coset) |
—
|
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: O(n) with O(n) = SO(n) ⊔ (reflection coset) | Statement: [SO(n), hasTwoComponentsIn, O(n) with O(n) = SO(n) ⊔ (reflection coset)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTwoComponentsIn Context triple: [SO(n), hasTwoComponentsIn, O(n) with O(n) = SO(n) ⊔ (reflection coset)]
-
A.
hasTwoPartStructure
chosen
Indicates that something is composed of exactly two distinct, structured parts that together form a whole.
-
B.
isComponentAlongWith
Indicates that an entity functions as a component in conjunction with one or more other components, typically forming a combined or complementary unit within a larger whole.
-
C.
hasTwoBranches
Indicates that the related entity is divided into or composed of exactly two distinct branches.
-
D.
isAComponentOf
Indicates that one entity functions as a constituent part or sub-unit of another, larger entity.
-
E.
hasTwoClasses
Indicates that an entity is associated with exactly two distinct classes or categories.
- 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_69e0b516293c819089458ea2ec85f85e |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736583c08819087a4726538e703e2 |
completed | April 21, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69e5f6161dac8190b06009cd180e3ff7 |
completed | April 20, 2026, 9:47 a.m. |
Created at: April 16, 2026, 4:02 p.m.