Triple
T16630417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eratosthenes spiral |
E404062
|
entity |
| Predicate | canBeAnalyzedUsing |
P30899
|
FINISHED |
| Object | computational experiments |
—
|
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: computational experiments | Statement: [Eratosthenes spiral, canBeAnalyzedUsing, computational experiments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeAnalyzedUsing Context triple: [Eratosthenes spiral, canBeAnalyzedUsing, computational experiments]
-
A.
hasAnalysis
Indicates that an entity is associated with, or has undergone, a particular analysis or examination.
-
B.
hasAnalysisType
Indicates that one entity is associated with, or characterized by, a specific type or category of analysis applied to it.
-
C.
helpsAnalyze
chosen
Indicates that one entity assists another in examining, interpreting, or understanding something in a more detailed or effective way.
-
D.
isAnalyticOn
Indicates that a function is analytic (holomorphic) throughout a specified domain or region.
-
E.
supportsInferenceOf
Indicates that one entity provides a logical basis or justification for concluding or deriving 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e378e4db5081908a6085f1bc2d65b8 |
completed | April 18, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.