Triple
T25638725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pasithee |
E642775
|
entity |
| Predicate | discoveryAnnouncement |
P60185
|
FINISHED |
| Object | International Astronomical Union Circular in 2002 |
—
|
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: International Astronomical Union Circular in 2002 | Statement: [Pasithee, discoveryAnnouncement, International Astronomical Union Circular in 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryAnnouncement Context triple: [Pasithee, discoveryAnnouncement, International Astronomical Union Circular in 2002]
-
A.
discoveryAnnouncementBy
chosen
Indicates that a particular entity publicly announces or reports the discovery of another entity or finding.
-
B.
hasDiscoveryAnnouncementDate
Indicates the date on which the discovery of an entity was formally announced or made public.
-
C.
publiclyAnnouncedBy
Indicates that an action, decision, or piece of information was formally communicated to the public by a specified agent or entity.
-
D.
discoveryConfirmed
Indicates that a previously identified potential discovery has been verified as valid or true.
-
E.
announcedTo
Indicates that one entity formally communicated or made known some information, decision, or event to another specific 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 5:38 p.m.