Triple
T14265176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peano arithmetic |
E353625
|
entity |
| Predicate | hasFunctionSymbol |
P56539
|
FINISHED |
| Object | successor function |
—
|
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: successor function | Statement: [Peano arithmetic, hasFunctionSymbol, successor function]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFunctionSymbol Context triple: [Peano arithmetic, hasFunctionSymbol, successor function]
-
A.
hasFunctionInPresent
Indicates that an entity currently performs, exhibits, or fulfills a specific function or role at the present time.
-
B.
containsFunction
chosen
Indicates that one entity includes, defines, or provides the implementation of a particular function.
-
C.
hasFunctionInLegends
Indicates that an entity serves a particular role, purpose, or activity within legendary stories, myths, or folklore.
-
D.
hasMainSymbol
Indicates that one entity is designated as the primary or most representative symbol associated with another entity.
-
E.
hasFunctionInComplex
Indicates that an entity performs a specific functional role within a larger molecular or structural complex.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6357a8188190ba518a486521052b |
completed | April 14, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:09 a.m.