Triple
T19468497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S/2012 (134340) 1 |
E487059
|
entity |
| Predicate | hasDiscoveryAnnouncementDate |
P136039
|
FINISHED |
| Object | 2012-07-11 |
—
|
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: 2012-07-11 | Statement: [S/2012 (134340) 1, hasDiscoveryAnnouncementDate, 2012-07-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiscoveryAnnouncementDate Context triple: [S/2012 (134340) 1, hasDiscoveryAnnouncementDate, 2012-07-11]
-
A.
discoveredSince
Indicates that one entity has been discovered starting from, or at some point after, a specified time or event associated with another entity.
-
B.
hasDiscoveryPeriod
Indicates the time span during which a particular discovery was made or recognized.
-
C.
hasDiscoveryStatus
Indicates the current state or phase of discovery or identification associated with an entity.
-
D.
discoveryAnnouncementBy
Indicates that a particular entity publicly announces or reports the discovery of another entity or finding.
-
E.
remainsDiscoveredOn
Indicates that the physical remains of an entity were found or uncovered at a particular location or site.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633e4b230819097c8804ee91988ea |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:39 p.m.