Triple
T35023104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Equuleus |
E1010248
|
entity |
| Predicate | discovererOrFirstCataloger |
P187083
|
FINISHED |
| Object | Ptolemy |
—
|
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: Ptolemy | Statement: [Equuleus, discovererOrFirstCataloger, Ptolemy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discovererOrFirstCataloger Context triple: [Equuleus, discovererOrFirstCataloger, Ptolemy]
-
A.
discovererDesignation
Indicates the identifier or designation assigned to the entity that discovered another entity.
-
B.
discoveredBy
Indicates that something was found, identified, or brought to light through the efforts or actions of a particular agent.
-
C.
subjectOfDiscovery
Indicates that an entity is the topic, object, or focus that has been discovered in a discovery event or process.
-
D.
discovererRole
Indicates the role or capacity in which an entity participates as the discoverer of something.
-
E.
eponymOfDiscovererOf
Indicates that one entity gives its name to the person who discovered 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb3424724c8190ba55ecf66fa0b171 |
completed | May 6, 2026, 12:29 p.m. |
Created at: May 3, 2026, 4:01 p.m.