Triple
T4202096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonoran Desert toad |
E86088
|
entity |
| Predicate | hasCommonNameOrigin |
P3325
|
FINISHED |
| Object | named after Sonoran Desert |
—
|
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: named after Sonoran Desert | Statement: [Sonoran Desert toad, hasCommonNameOrigin, named after Sonoran Desert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonNameOrigin Context triple: [Sonoran Desert toad, hasCommonNameOrigin, named after Sonoran Desert]
-
A.
includesCommonName
Indicates that one entity contains or specifies a commonly used (non-scientific) name for another entity.
-
B.
hasNameOrigin
chosen
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
C.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
D.
commonNameOf
Indicates that one entity is the commonly used or popular name by which the other entity is known.
-
E.
hasCommonAncestryGroup
Indicates that the related entities share membership in the same ancestral or lineage-based group.
- 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af037f1de4819088d6bf544317a694 |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af01959c4881909eb1adcb3bdadbe6 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:49 p.m.