Triple
T28830848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canis lycaon |
E728043
|
entity |
| Predicate | relatedCommonName |
P570
|
FINISHED |
| Object | gray wolf |
—
|
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: gray wolf | Statement: [Canis lycaon, relatedCommonName, gray wolf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedCommonName Context triple: [Canis lycaon, relatedCommonName, gray wolf]
-
A.
otherCommonName
Indicates that an entity is known by an additional, alternative common name besides its primary one.
-
B.
moreCommonPublicName
Indicates that one name is used more frequently or popularly in public contexts than another alternative name for the same entity.
-
C.
commonlyLinkedTo
Indicates that one entity is frequently or typically associated, connected, or co-occurring with another entity.
-
D.
commonName
chosen
Indicates that one entity is the commonly used or vernacular name by which the other entity is known.
-
E.
associatedName
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a008ac37dc081908d360574912f40ec |
completed | May 10, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_6a008a67d73881909855ab4cfca3c399 |
completed | May 10, 2026, 1:38 p.m. |
Created at: April 28, 2026, 6:37 a.m.