Triple
T29768388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta Mensids |
E753978
|
entity |
| Predicate | meteoroidComposition |
P167862
|
FINISHED |
| Object | cometary material |
—
|
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: cometary material | Statement: [Delta Mensids, meteoroidComposition, cometary material]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meteoroidComposition Context triple: [Delta Mensids, meteoroidComposition, cometary material]
-
A.
meteoriteType
Indicates the classification or category of a meteorite based on its composition or characteristics.
-
B.
meteoroidSource
Indicates that one entity is the origin or source from which the meteoroid represented by the other entity comes.
-
C.
meteoriteClass
Indicates the classification category or type assigned to a meteorite based on its composition or characteristics.
-
D.
dustComposition
Indicates the material makeup or constituent substances that form a given dust sample or dust population.
-
E.
isMonolithicOrRubblePile
Indicates whether an object exists as a single coherent body or as a loosely bound aggregate of smaller pieces (a rubble pile).
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6745f8354819085a81de5c32dd49e |
completed | May 2, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 28, 2026, 8:40 p.m.