Triple
T16630382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eratosthenes spiral |
E404062
|
entity |
| Predicate | arranges |
P123636
|
FINISHED |
| Object | positive integers |
—
|
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: positive integers | Statement: [Eratosthenes spiral, arranges, positive integers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arranges Context triple: [Eratosthenes spiral, arranges, positive integers]
-
A.
arrangement
Indicates a relationship where entities are organized, ordered, or positioned in a particular configuration or sequence relative to one another.
-
B.
commonlyArrangedFor
Indicates that one entity is typically organized, scheduled, or set up on behalf of another entity.
-
C.
isArrangementOf
Indicates that one entity is a specific ordering or configuration of the components or elements of another entity.
-
D.
arrangementType
Indicates the specific kind or category of arrangement that characterizes how the related entities are organized or structured in relation to each other.
-
E.
canBeArrangedFor
Indicates that one entity is able to be scheduled, organized, or set up on behalf of or for the benefit of another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:17 a.m.