Triple
T10829108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Veblen hierarchy |
E255569
|
entity |
| Predicate | constructionDetail |
P7599
|
FINISHED |
| Object | φ_{α+1} enumerates common fixed points of φ_α |
—
|
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: φ_{α+1} enumerates common fixed points of φ_α | Statement: [Veblen hierarchy, constructionDetail, φ_{α+1} enumerates common fixed points of φ_α]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: constructionDetail
Context triple: [Veblen hierarchy, constructionDetail, φ_{α+1} enumerates common fixed points of φ_α]
-
A.
constructionBase
Indicates that one entity serves as the foundational structure or base upon which another entity is constructed or built.
-
B.
constructionType
chosen
Indicates the specific method or style by which something is built or constructed.
-
C.
constructionDirection
Indicates the orientation or path along which a structure is built or assembled.
-
D.
constructionForm
Indicates the method, style, or structural technique by which something is built or constructed.
-
E.
constructionCharacteristic
Indicates a specific structural or material property that characterizes how something is built or constructed.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d734d3eab88190b30a3025b6b2b0bc |
completed | April 9, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.