Triple
T22863201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morchella americana |
E566979
|
entity |
| Predicate | hasCommonName |
P570
|
FINISHED |
| Object | American morel |
—
|
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: American morel | Statement: [Morchella americana, hasCommonName, American morel]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: American morel Context triple: [Morchella americana, hasCommonName, American morel]
-
A.
Morchella americana
chosen
Morchella americana is a species of edible morel mushroom native to North America, known for its honeycomb-like cap and culinary value.
-
B.
Morel
Morel is a Spanish-origin surname borne by various notable individuals across the Spanish-speaking world.
-
C.
Morchella esculenta
Morchella esculenta is a highly prized edible morel mushroom species known for its honeycomb-like cap and rich, nutty flavor.
-
D.
Morchella
Morchella is a genus of distinctive honeycomb-like edible mushrooms commonly known as morels, prized in culinary traditions worldwide.
-
E.
Morchella conica
Morchella conica is a species of morel mushroom known for its distinctive conical, honeycombed cap and culinary value as an edible wild fungus.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eff1c18819081dc9dfc1816f746 |
completed | April 29, 2026, 3:46 a.m. |
Created at: April 17, 2026, 3:38 p.m.