Triple
T5043934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C/1996 B2 |
E113612
|
entity |
| Predicate | causedEnhancedCometResearch |
P60988
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [C/1996 B2, causedEnhancedCometResearch, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causedEnhancedCometResearch Context triple: [C/1996 B2, causedEnhancedCometResearch, true]
-
A.
experimentedOn
Indicates that one entity conducted experiments or tests on another entity as the subject of investigation.
-
B.
mayHaveIncreasedResearchFreedom
Indicates that an entity is permitted or enabled to conduct research with fewer restrictions or greater autonomy than before.
-
C.
notableExperiment
Indicates that an entity is recognized for having conducted or been the subject of a particularly important or influential experiment.
-
D.
hasResearchFinding
Indicates that an entity has produced, contains, or is associated with a specific research finding or result.
-
E.
supportedResearch
Indicates that one entity provided assistance, resources, or backing to enable or advance the research activities of another entity.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73fc04f08190aba851fa0192d0fb |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71529d608190a53470ba6c14bb1d |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd73617f348190b2fa68a0ef4fc7b1 |
completed | March 20, 2026, 4:18 p.m. |
Created at: March 20, 2026, 1:37 p.m.