Triple
T7017005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | hoolock gibbon |
E162721
|
entity |
| Predicate | firstDescribedAsGenus |
P25254
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [hoolock gibbon, firstDescribedAsGenus, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDescribedAsGenus Context triple: [hoolock gibbon, firstDescribedAsGenus, 2005]
-
A.
firstDescribedAs
chosen
Indicates the original way or terms in which something was initially characterized, named, or documented.
-
B.
hasGenus
Indicates that one entity belongs to, or is classified under, the biological genus represented by the other entity.
-
C.
recognizedAsDistinctSpeciesSince
Indicates that an organism or taxon has been formally acknowledged and classified as a separate species starting from a specified point in time.
-
D.
previousGenus
Indicates that one genus was previously used as the taxonomic genus for an organism before being reclassified to another genus.
-
E.
officiallyDescribedAs
Indicates that an entity is formally characterized or defined using a specific description in an official or authoritative context.
- 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_69c6885a127c8190867b059bdccf13ff |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b8118481909d76eb6616160e80 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:34 p.m.