Triple
T25215848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | corpus of Archimedes |
E631824
|
entity |
| Predicate | hasImportantSource |
P60019
|
FINISHED |
| Object | Archimedes Palimpsest |
—
|
NE NERFINISHED |
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: Archimedes Palimpsest | Statement: [corpus of Archimedes, hasImportantSource, Archimedes Palimpsest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImportantSource Context triple: [corpus of Archimedes, hasImportantSource, Archimedes Palimpsest]
-
A.
hasMainSource
chosen
Indicates that one entity serves as the primary or principal source or origin for another entity.
-
B.
isMajorSourceOf
Indicates that one entity serves as a primary or dominant origin, cause, or provider of another entity or effect.
-
C.
hasSecondarySource
Indicates that an entity is supported, documented, or referenced by a secondary source rather than by a primary or original source.
-
D.
containsSourceOf
Indicates that one entity includes, holds, or encompasses the origin or cause of another entity.
-
E.
isImportantFor
Indicates that something holds significant value, relevance, or necessity in relation to something else.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 21, 2026, 12:59 p.m.