Triple
T31553156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orthrias |
E805057
|
entity |
| Predicate | hasCommonNameGroup |
P73622
|
FINISHED |
| Object | loaches |
—
|
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: loaches | Statement: [Orthrias, hasCommonNameGroup, loaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonNameGroup Context triple: [Orthrias, hasCommonNameGroup, loaches]
-
A.
commonNameGroup
chosen
Indicates that multiple entities share the same commonly used name or are grouped under a single common name.
-
B.
hasCommonAncestryGroup
Indicates that the related entities share membership in the same ancestral or lineage-based group.
-
C.
includesCommonName
Indicates that one entity contains or specifies a commonly used (non-scientific) name for another entity.
-
D.
hasTribeCommonName
Indicates that two entities are related by the commonly used (vernacular) name of a tribe.
-
E.
isConsideredCommonNameIn
Indicates that a given name is regarded as the commonly used or standard name for an entity within a specified context, region, or language.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a02f441bd408190923b6b68adee8fde |
completed | May 12, 2026, 9:34 a.m. |
| PD | Predicate disambiguation | batch_6a02f3c1e64881908569423c9f298f26 |
completed | May 12, 2026, 9:32 a.m. |
Created at: April 30, 2026, 10:12 p.m.