Triple
T34655273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludi Victoriae Caesaris |
E889957
|
entity |
| Predicate | linkedAstronomicalPhenomenon |
P61225
|
FINISHED |
| Object | great comet of 44 BC |
—
|
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: great comet of 44 BC | Statement: [Ludi Victoriae Caesaris, linkedAstronomicalPhenomenon, great comet of 44 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedAstronomicalPhenomenon Context triple: [Ludi Victoriae Caesaris, linkedAstronomicalPhenomenon, great comet of 44 BC]
-
A.
observedAstronomicalEvent
Indicates that an entity has witnessed, detected, or recorded a specific astronomical event.
-
B.
relatedAstronomicalObject
Indicates that one astronomical object has a specified relationship or association with another astronomical object.
-
C.
marksAstronomicalEvent
chosen
Indicates that one entity serves as a sign, boundary, or reference point denoting the occurrence or timing of an astronomical event.
-
D.
isLinkedToAstronomy
Indicates that something has a connection or relevant association to the field or study of astronomy.
-
E.
observedAstronomicalBody
Indicates that an entity has observed, detected, or recorded data about a particular astronomical body.
- 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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: May 1, 2026, 2:04 a.m.