Triple
T12689621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Willamette Meteorite |
E303166
|
entity |
| Predicate | estimatedOrigin |
P82776
|
FINISHED |
| Object | asteroid belt |
—
|
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: asteroid belt | Statement: [Willamette Meteorite, estimatedOrigin, asteroid belt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedOrigin Context triple: [Willamette Meteorite, estimatedOrigin, asteroid belt]
-
A.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
B.
hasApproximateOrigin
chosen
Indicates that an entity originates from a source or location that is known only approximately rather than precisely.
-
C.
physicalOrigin
Indicates that one entity is the place or source from which another entity physically originates or comes into existence.
-
D.
originSite
Indicates the place or site from which something or someone originally comes or is derived.
-
E.
missionOrigin
Indicates the place, organization, or context from which a mission is initiated or originates.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:21 p.m.