Triple
T28677637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitrospingidae |
E725911
|
entity |
| Predicate | recognizedAsDistinctBasedOn |
P14118
|
FINISHED |
| Object | genetic evidence |
—
|
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: genetic evidence | Statement: [Mitrospingidae, recognizedAsDistinctBasedOn, genetic evidence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizedAsDistinctBasedOn Context triple: [Mitrospingidae, recognizedAsDistinctBasedOn, genetic evidence]
-
A.
recognizedAs
Indicates that one entity is acknowledged or accepted as having the identity, role, status, or classification of another entity.
-
B.
isDistinguishedBy
chosen
Indicates that one entity is characterized or set apart from others by a particular feature, quality, or attribute.
-
C.
recognizedAsDistinctLanguageFrom
Indicates that one language is formally acknowledged or treated as a separate and distinct language from another, rather than as a dialect or variant of it.
-
D.
isDistinctFrom
Indicates that two entities are not identical and can be clearly distinguished from one another.
-
E.
recognizedSee
Indicates that one entity sees another and consciously recognizes or identifies what is being seen.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 28, 2026, 5:07 a.m.