Triple
T24807239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gelon II of Syracuse |
E620686
|
entity |
| Predicate | patronOfPerson |
P68473
|
FINISHED |
| Object | Archimedes |
—
|
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 | Statement: [Gelon II of Syracuse, patronOfPerson, Archimedes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patronOfPerson Context triple: [Gelon II of Syracuse, patronOfPerson, Archimedes]
-
A.
familyPatronOf
Indicates a relationship where one family acts as a patron, sponsor, or protector providing support or resources to another party.
-
B.
patronOfWork
Indicates that one entity financially supports or sponsors the creation, performance, or exhibition of a particular work produced by another entity.
-
C.
usedAsPatronOf
chosen
Indicates that one entity serves as a patron or sponsor for another, providing support, endorsement, or backing.
-
D.
patroness
Indicates that a female person supports, sponsors, or acts as a benefactor for someone or something.
-
E.
patronFamilyOf
Indicates a familial relationship in which one family acts as a patron, protector, or benefactor to another family.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:50 a.m.