Triple
T37205861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tau Herculids |
E922166
|
entity |
| Predicate | parentCometOrbitalPeriod |
P2028
|
FINISHED |
| Object | about 5.4 years |
—
|
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: about 5.4 years | Statement: [Tau Herculids, parentCometOrbitalPeriod, about 5.4 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentCometOrbitalPeriod Context triple: [Tau Herculids, parentCometOrbitalPeriod, about 5.4 years]
-
A.
parentCometPerihelionInterval
Indicates the time interval between successive perihelion passages of a parent comet associated with another object or event.
-
B.
parentCometInclination
Indicates the orbital inclination of a comet’s parent body relative to a reference plane.
-
C.
parentCometDesignation
Indicates that one entity is the official designation of the parent comet from which another entity (such as a meteor shower or fragment) originates.
-
D.
hasOrbitalPeriod
chosen
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
E.
parentCometType
Indicates the type or classification of the comet from which another object (such as a meteor stream or fragment) originates.
- 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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: May 3, 2026, 4:15 p.m.