Triple
T692839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peano notation |
E13831
|
entity |
| Predicate | notationStyle |
P5329
|
FINISHED |
| Object | unary numeral system |
—
|
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: unary numeral system | Statement: [Peano notation, notationStyle, unary numeral system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notationStyle Context triple: [Peano notation, notationStyle, unary numeral system]
-
A.
notationType
Indicates the specific system or style of notation used to represent or encode something (such as music, math, or language).
-
B.
notationPattern
chosen
Indicates a recurring way in which something is symbolically represented or written, such as a consistent style or structure of notation used for an entity or concept.
-
C.
notation
Indicates a conventional way of symbolically representing or writing something, such as concepts, quantities, or operations, within a specific system.
-
D.
notationSystem
Indicates a relationship where one entity is the system or method of notation used to represent or encode another entity.
-
E.
typicalNotation
Indicates that one entity is the standard or commonly used symbolic representation (notation) for 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0b05f2c8190876c73db15b489a2 |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d221d38819083c0adda81f59b07 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.