Triple
T24916305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OEIS A002850 |
E623992
|
entity |
| Predicate | hasCrossReferences |
P111150
|
FINISHED |
| Object | other OEIS sequences |
—
|
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: other OEIS sequences | Statement: [OEIS A002850, hasCrossReferences, other OEIS sequences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrossReferences Context triple: [OEIS A002850, hasCrossReferences, other OEIS sequences]
-
A.
hasReferences
Indicates that one entity cites, points to, or relies on another entity as a reference or source.
-
B.
crossReference
chosen
Indicates that one entity refers the user to another related entity or source for additional or supporting information.
-
C.
hasCross
Indicates that one entity possesses, displays, or is marked by a cross in relation to another entity or context.
-
D.
hasCommonReference
Indicates that two or more entities share the same source, citation, or referential basis.
-
E.
crossesAssociatedWith
Indicates a relationship where one entity’s crossing or intersection is functionally or contextually linked 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:28 a.m.