Triple
T9456432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ørsted (crater on Mercury) |
E228025
|
entity |
| Predicate | eponymNotableFor |
P47121
|
FINISHED |
| Object | electromagnetism |
—
|
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: electromagnetism | Statement: [Ørsted (crater on Mercury), eponymNotableFor, electromagnetism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eponymNotableFor Context triple: [Ørsted (crater on Mercury), eponymNotableFor, electromagnetism]
-
A.
eponymFor
chosen
Indicates that one entity gives its name to another entity, which is then named after it.
-
B.
eponymCountry
Indicates that a country is named after (or serves as the namesake for) a particular person, place, or entity.
-
C.
hasEponymConnectionTo
Indicates that one entity is named after, derived from, or otherwise linguistically or honorifically connected to another entity as its eponym.
-
D.
sharesEponymWith
Indicates that two entities are named after the same person, place, or thing (i.e., they share the same eponym).
-
E.
eponymLanguage
Indicates that a language is named after (is the eponym of) a particular person, place, or entity.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f8f7e1481909318e473ab4d6460 |
completed | April 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69cca5596ffc819097e9c8eefd4ef9b8 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:52 p.m.