Triple
T2535340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mespilus |
E56254
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | Pyrus |
E56514
|
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: Pyrus | Statement: [Mespilus, relatedTo, Pyrus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pyrus Context triple: [Mespilus, relatedTo, Pyrus]
-
A.
Pyrus
chosen
Pyrus is a genus of flowering plants best known for including the cultivated pear trees that produce edible pears.
-
B.
Malus
Malus is a genus of deciduous trees and shrubs in the rose family best known for cultivated apples and ornamental crabapples.
-
C.
Naran
Naran is a popular mountain resort town and tourist destination in northern Pakistan, known for its scenic valleys, rivers, and access to sites like Lake Saif-ul-Malook.
-
D.
Banna
Banna is the Latin name of Birdoswald Roman Fort, a key military site along Hadrian’s Wall in Roman Britain.
-
E.
Aegle
Aegle is a figure from Greek mythology, often identified as one of the Hesperides, the nymphs associated with a blissful garden at the western edge of the world.
- 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_69ab4a49b6508190bc467fbef4bac334 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd27c8650819080005869789b802c |
completed | March 7, 2026, 7:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af2bbf248481908f588bc1cf46d168 |
completed | March 9, 2026, 8:21 p.m. |
Created at: March 6, 2026, 9:47 p.m.