Triple
T23234953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | orthogonal group O(n+1,2) |
E581259
|
entity |
| Predicate | hasRankOverℂ |
P151472
|
FINISHED |
| Object | ⌊(n+3)/2⌋ |
—
|
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: ⌊(n+3)/2⌋ | Statement: [orthogonal group O(n+1,2), hasRankOverℂ, ⌊(n+3)/2⌋]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankOverℂ Context triple: [orthogonal group O(n+1,2), hasRankOverℂ, ⌊(n+3)/2⌋]
-
A.
rankOverℤ
Indicates that one entity has a higher (or superior) rank than another when ranks are compared as integers over the set of all integers ℤ.
-
B.
dimensionAsVectorSpaceOverℚ
Indicates that the dimension of a given vector space is being considered specifically as a vector space over the field of rational numbers ℚ.
-
C.
containsRank
Indicates that one entity includes or encompasses another entity that has a specific rank or hierarchical level within it.
-
D.
typicalRank
Indicates the usual or most common rank or position an entity holds within a given ordering or hierarchy.
-
E.
typicalRankRange
Indicates the usual or most common range of ranks or ordered positions that an entity typically occupies within a ranking or hierarchy.
- F. None of above. chosen
Provenance (4 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192e8c7548190b53434eeb2620a6e |
completed | April 29, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d8770d081908897c28b04e5faea |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 17, 2026, 4:09 p.m.