Triple
T32941081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hylophilus |
E842665
|
entity |
| Predicate | isCommonNameFor |
P1354
|
FINISHED |
| Object | several small greenish vireo-like birds |
—
|
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: several small greenish vireo-like birds | Statement: [Hylophilus, isCommonNameFor, several small greenish vireo-like birds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonNameFor Context triple: [Hylophilus, isCommonNameFor, several small greenish vireo-like birds]
-
A.
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.
-
B.
includesCommonName
Indicates that one entity contains or specifies a commonly used (non-scientific) name for another entity.
-
C.
commonNameOf
chosen
Indicates that one entity is the commonly used or popular name by which the other entity is known.
-
D.
commonName
Indicates that one entity is the commonly used or vernacular name by which the other entity is known.
-
E.
lessCommonNameFor
Indicates that the subject is a less commonly used name or label for the same entity or concept as the object.
- 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 1:20 a.m.