Triple
T28656724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minuscule 565 |
E725353
|
entity |
| Predicate | SodenNumber |
P85109
|
FINISHED |
| Object | ε 93 |
—
|
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: ε 93 | Statement: [Minuscule 565, SodenNumber, ε 93]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SodenNumber Context triple: [Minuscule 565, SodenNumber, ε 93]
-
A.
vonSodenNumber
chosen
Indicates the standardized catalog number assigned to a manuscript or text according to von Soden’s classification system.
-
B.
SSNumber
Indicates that an entity has a specific Social Security Number assigned to it.
-
C.
serialNumber
Indicates a unique identifying code assigned to an individual item or instance within a series or batch.
-
D.
saoNumber
Indicates a relationship where an entity is identified or referenced by its SAO (Smithsonian Astrophysical Observatory) catalog number.
-
E.
ISONumber
Indicates that an entity is associated with, identified by, or conforms to a specific ISO (International Organization for Standardization) number or standard.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:55 a.m.