Triple
T3867985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunday |
E91907
|
entity |
| Predicate | hasPlanetAssociation |
P2830
|
FINISHED |
| Object | Sun in classical astrology |
—
|
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: Sun in classical astrology | Statement: [Sunday, hasPlanetAssociation, Sun in classical astrology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlanetAssociation Context triple: [Sunday, hasPlanetAssociation, Sun in classical astrology]
-
A.
hasPlanet
Indicates that one entity possesses, contains, or is associated with a particular planet as part of its system or domain.
-
B.
isAssociatedWith
chosen
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
C.
hasCandidatePlanet
Indicates that an object (typically a star or system) is associated with a planet that is suspected or proposed to exist but not yet fully confirmed.
-
D.
hasDwarfPlanet
Indicates that one entity possesses or is associated with a dwarf planet as part of its system or domain.
-
E.
relatedAstronomicalObject
Indicates that one astronomical object has a specified relationship or association with another astronomical object.
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec3cc1a88190924125a86f72fd5b |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.