Triple
T37205878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tau Herculids |
E922166
|
entity |
| Predicate | radiantReferenceStar |
P187536
|
FINISHED |
| Object | Tau Herculis |
—
|
NE NERFINISHED |
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: Tau Herculis | Statement: [Tau Herculids, radiantReferenceStar, Tau Herculis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radiantReferenceStar Context triple: [Tau Herculids, radiantReferenceStar, Tau Herculis]
-
A.
centralStarApparentMagnitude
Indicates the apparent brightness (as seen from a given vantage point) of a system’s central star, expressed in astronomical magnitude.
-
B.
brightestStar
Indicates that one entity is the most luminous star within a specified group, region, or context relative to the others.
-
C.
radiantStarRegion
Indicates a region in space that is prominently illuminated or dominated by the radiance of a particular star.
-
D.
radiantIn
Indicates that one entity emits or shines light, energy, or brilliance within or into another entity or space.
-
E.
targetStarType
Indicates the specific classification or type of star that serves as the target in a given relationship or context.
- 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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb55dc36d08190a0634fa680e13114 |
completed | May 6, 2026, 2:53 p.m. |
Created at: May 3, 2026, 4:15 p.m.