Triple
T17167742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arabidopsis |
E416648
|
entity |
| Predicate | nativeTo |
P410
|
FINISHED |
| Object | Eurasia |
E9404
|
NE 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: Eurasia | Statement: [Arabidopsis, nativeTo, Eurasia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eurasia Context triple: [Arabidopsis, nativeTo, Eurasia]
-
A.
Eurasia
chosen
Eurasia is the vast combined continental landmass of Europe and Asia, forming the largest continuous land area on Earth.
-
B.
Euravia
Euravia was the original name of the British charter airline that later became known as Britannia Airways.
-
C.
Asia–Europe
Asia–Europe is a major intercontinental shipping and trade route connecting key ports across the Asian and European continents.
-
D.
Afro-Eurasia
Afro-Eurasia is the vast continuous landmass comprising the continents of Africa, Europe, and Asia, forming the largest connected continental area on Earth.
-
E.
Eastern Eurasia
Eastern Eurasia is the broad eastern portion of the Eurasian landmass, encompassing regions such as East Asia, parts of Siberia, and adjacent steppe and coastal areas that have long been central to transcontinental trade and cultural exchange.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f916833c81909c64e0d74b40a85b |
completed | April 18, 2026, 9:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01483d754c819089607cfc87d08d42 |
completed | May 11, 2026, 3:08 a.m. |
Created at: April 10, 2026, 5:37 a.m.