Triple
T24822599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OEIS A002849 |
E621099
|
entity |
| Predicate | hasOffset |
P158677
|
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 A002849, hasOffset, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOffset Context triple: [OEIS A002849, hasOffset, 0]
-
A.
hasTimeOffset
Indicates that one temporal value is shifted or displaced from another by a specified amount of time.
-
B.
isOffsetFrom
Indicates that one entity’s position, value, or occurrence is displaced by a specified amount or direction relative to another entity.
-
C.
usesOffsetFrom
Indicates that one entity determines or expresses its position, value, or behavior relative to another by applying a specified offset from that reference.
-
D.
hasOffsetNullPins
Indicates that one entity has pins that are offset from a reference position and intentionally left unconnected or null.
-
E.
hasInputOffsetNullCapability
Indicates that an entity supports or is capable of handling input values that are null or have no offset.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f47b7f657c81908174590c811a3cbf |
completed | May 1, 2026, 10:07 a.m. |
Created at: April 18, 2026, 5:04 a.m.