Triple
T8577526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comet 67P/Churyumov–Gerasimenko |
E203083
|
entity |
| Predicate | hasDust |
P82946
|
FINISHED |
| Object | silicate particles |
—
|
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: silicate particles | Statement: [Comet 67P/Churyumov–Gerasimenko, hasDust, silicate particles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDust Context triple: [Comet 67P/Churyumov–Gerasimenko, hasDust, silicate particles]
-
A.
hasDustLanes
Indicates that an object exhibits distinct, lane-like regions of dust that obscure or separate its brighter components.
-
B.
hasDunes
Indicates that one entity (typically a geographic area or surface) possesses or is characterized by sand dunes.
-
C.
hasSedimentsThat
Indicates that one entity contains, includes, or is associated with specific sediments described by the related entity.
-
D.
hasExtendedDustyRegion
Indicates that an entity possesses a surrounding area or zone characterized by dust that extends outward beyond its immediate vicinity.
-
E.
hasSand
Indicates that something contains, is covered with, or is characterized by the presence of sand.
- 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_69ca8328ebe481909a8c038fa79959b4 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea97787481909ebbaa45f59cbdaa |
completed | March 31, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69cbd11b13108190b07f8f161425a585 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:22 p.m.