Triple
T24248898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herschel crater |
E603456
|
entity |
| Predicate | namedForDiscoveryOf |
P155325
|
FINISHED |
| Object | planet Uranus by William Herschel |
—
|
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: planet Uranus by William Herschel | Statement: [Herschel crater, namedForDiscoveryOf, planet Uranus by William Herschel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedForDiscoveryOf Context triple: [Herschel crater, namedForDiscoveryOf, planet Uranus by William Herschel]
-
A.
knownForDiscovering
Indicates that one entity is recognized or notable for having discovered another entity.
-
B.
isDiscoveredBy
Indicates that something (such as an object, fact, or phenomenon) is found, identified, or revealed by a particular agent or entity.
-
C.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
D.
discovery
Indicates the event or process by which one entity finds, uncovers, or identifies something previously unknown or unrecognized.
-
E.
inspiredDiscoveryOf
Indicates that one entity’s ideas, actions, or work motivated or led directly to another entity’s discovery.
- 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_69e29540da0481909a38bdae315b7a02 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28b87d03c8190a38ca0c0b65ce6fc |
completed | April 29, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 12:04 a.m.