Triple
T38414278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meteor Crater |
E901562
|
entity |
| Predicate | impactorType |
P191940
|
FINISHED |
| Object | nickel-iron meteorite |
—
|
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: nickel-iron meteorite | Statement: [Meteor Crater, impactorType, nickel-iron meteorite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactorType Context triple: [Meteor Crater, impactorType, nickel-iron meteorite]
-
A.
impactor
Indicates that one entity exerts a forceful contact or collision upon another, typically causing a physical impact or change.
-
B.
impactorDiameter
Indicates the size of the object that impacts another body, typically measured as the diameter of the impacting body.
-
C.
implementationType
Indicates the specific manner or approach by which something is implemented or realized in practice.
-
D.
integratorType
Indicates the specific kind or category of integrator associated with or used in relation to an entity.
-
E.
IntimidatorType
Indicates that one entity acts as a source or type of intimidation toward 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_69f76e61e79c81908b787d83b46ab92b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69fcef636dfc819085cf91323f2e4edd |
completed | May 7, 2026, 8 p.m. |
Created at: May 3, 2026, 4:31 p.m.