Triple
T37205862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tau Herculids |
E922166
|
entity |
| Predicate | parentCometBreakup |
P196847
|
FINISHED |
| Object | major fragmentation in 1995 |
—
|
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: major fragmentation in 1995 | Statement: [Tau Herculids, parentCometBreakup, major fragmentation in 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentCometBreakup Context triple: [Tau Herculids, parentCometBreakup, major fragmentation in 1995]
-
A.
parentCometType
Indicates the type or classification of the comet from which another object (such as a meteor stream or fragment) originates.
-
B.
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.
-
C.
breaksUpIn
Indicates that one entity ends or dissolves a relationship or partnership with another entity.
-
D.
parentCometInclination
Indicates the orbital inclination of a comet’s parent body relative to a reference plane.
-
E.
coParentWith
Indicates that two individuals share at least one child together, jointly occupying a parental role for that child.
- 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_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
| PDg | Predicate description generation | batch_69fe6b7a823881909dc2037fe25bea24 |
completed | May 8, 2026, 11:02 p.m. |
Created at: May 3, 2026, 4:15 p.m.