Triple
T1358687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sidereus Nuncius |
E29047
|
entity |
| Predicate | reportsDiscoveryOf |
P27994
|
FINISHED |
| Object | mountains on the Moon |
—
|
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: mountains on the Moon | Statement: [Sidereus Nuncius, reportsDiscoveryOf, mountains on the Moon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportsDiscoveryOf Context triple: [Sidereus Nuncius, reportsDiscoveryOf, mountains on the Moon]
-
A.
discovery
Indicates the event or process by which one entity finds, uncovers, or identifies something previously unknown or unrecognized.
-
B.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
C.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
D.
reportsDecisionsOf
Indicates that one entity communicates or provides information about the decisions made by another entity.
-
E.
discoveredSince
Indicates that one entity has been discovered starting from, or at some point after, a specified time or event associated with 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c28f5b988190b0be4504eabb919d |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef7700c819099b294e8d9320e70 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c20fd1fc8190977a768b1ed2d23b |
completed | March 1, 2026, 10:47 p.m. |
Created at: March 1, 2026, 7:56 p.m.