Triple
T34703223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allende meteorite fall |
E1000430
|
entity |
| Predicate | meteoriteNameAbbreviation |
P181708
|
FINISHED |
| Object | Allende (CV3) |
—
|
NE NERFINISHED |
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: Allende (CV3) | Statement: [Allende meteorite fall, meteoriteNameAbbreviation, Allende (CV3)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meteoriteNameAbbreviation Context triple: [Allende meteorite fall, meteoriteNameAbbreviation, Allende (CV3)]
-
A.
meteoriteName
chosen
Indicates that an entity (such as a sample, event, or record) is associated with a specific named meteorite.
-
B.
meteoriteType
Indicates the classification or category of a meteorite based on its composition or characteristics.
-
C.
meteoriteClass
Indicates the classification category or type assigned to a meteorite based on its composition or characteristics.
-
D.
meteoriteGroup
Indicates a classification relationship where a meteorite is assigned to a specific group based on its shared characteristics or origin.
-
E.
meteoriteStruck
Indicates that a meteorite collided with and impacted a particular target or location.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 3:59 p.m.