Triple
T2307346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hesperus |
E51869
|
entity |
| Predicate | astronomicalPhase |
P39088
|
FINISHED |
| Object | evening apparition of Venus |
—
|
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: evening apparition of Venus | Statement: [Hesperus, astronomicalPhase, evening apparition of Venus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: astronomicalPhase Context triple: [Hesperus, astronomicalPhase, evening apparition of Venus]
-
A.
phaseOfSeason
Indicates that one temporal segment represents a specific phase or part within a larger season.
-
B.
lunarCalendar
Indicates that the referenced system, event, or date is defined, measured, or scheduled according to a calendar based on the phases or cycles of the Moon.
-
C.
endDateSidereal
Indicates the date and time, measured in sidereal rather than solar terms, at which a specified event, state, or interval comes to an end.
-
D.
moonSightingRole
Indicates the specific role or capacity an entity has in the context of observing, reporting, or validating a moon sighting.
-
E.
largeMoon
Indicates that a moon has a size or diameter significantly greater than a typical or reference moon.
- 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abce1f4f0c8190a714e4dcb8449f7e |
completed | March 7, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69abc58ce2a081908ce2f0cadd92e9f8 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abce1e7c788190a15890feb2437f1d |
completed | March 7, 2026, 7:05 a.m. |
Created at: March 4, 2026, 7:49 p.m.