Triple
T20851743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feferman–Schütte ordinal |
E513379
|
entity |
| Predicate | roleInProofTheory |
P67072
|
FINISHED |
| Object | ordinal of predicative analysis |
—
|
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: ordinal of predicative analysis | Statement: [Feferman–Schütte ordinal, roleInProofTheory, ordinal of predicative analysis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInProofTheory Context triple: [Feferman–Schütte ordinal, roleInProofTheory, ordinal of predicative analysis]
-
A.
proofRole
Indicates the specific function or responsibility an entity has within the structure or presentation of a proof.
-
B.
roleInTheory
chosen
Indicates the specific function, position, or contribution that an entity has within a particular theory or theoretical framework.
-
C.
roleInHerbrandTheorem
Indicates that an entity participates in or contributes to the application, formulation, or proof of Herbrand’s theorem.
-
D.
roleInReasonML
Indicates that an entity holds a specific role or function within the ReasonML language, ecosystem, or community.
-
E.
usesProofLanguage
Indicates that one entity employs a specific formal or structured language to express or present a proof related to another entity.
- 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_69e0b4f4898081908209e58edb8f9c45 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3a3d8808190b8efce77ae36850e |
completed | April 21, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:43 p.m.