Triple
T6833578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OEIS A064988 |
E157394
|
entity |
| Predicate | startsWithIntegerPart |
P73429
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [OEIS A064988, startsWithIntegerPart, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startsWithIntegerPart Context triple: [OEIS A064988, startsWithIntegerPart, 0]
-
A.
firstPartRepresents
Indicates that the initial segment or portion of something stands for, symbolizes, or denotes a larger whole or specific concept.
-
B.
isInteger
Indicates that a given value represents a whole number with no fractional or decimal component.
-
C.
hasIntegralRepresentation
Indicates that one entity can be expressed or represented as an integral involving the other entity.
-
D.
containsNumber
Indicates that one entity includes or has at least one numeric value or digit within it.
-
E.
hasIntegerCaseStatement
Indicates that an entity includes or is associated with a case statement whose controlling expression is an integer value.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d62b1e8c8190a81d91191a54b073 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d623aba88190a93ec9c83508c960 |
completed | March 27, 2026, 7:10 p.m. |
Created at: March 27, 2026, 2:18 p.m.