Triple
T3837805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ewondo language |
E91177
|
entity |
| Predicate | hasGuthrieCode |
P18539
|
FINISHED |
| Object | A72 |
—
|
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: A72 | Statement: [Ewondo language, hasGuthrieCode, A72]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGuthrieCode Context triple: [Ewondo language, hasGuthrieCode, A72]
-
A.
guthrieClassification
chosen
Indicates a categorization relationship where an entity is assigned a class or type according to the Guthrie classification system.
-
B.
geneticStatus
Indicates the genetic condition or variant state an entity has in relation to a specific gene or set of genes.
-
C.
hasChapmanCode
Indicates that an entity (typically a geographic or administrative area) is associated with a specific Chapman code used for standardized location identification.
-
D.
hasATCCode
Indicates that a pharmaceutical product or substance is assigned a specific Anatomical Therapeutic Chemical (ATC) classification code.
-
E.
hasHerbariumCode
Indicates that an institution or collection is associated with a specific standardized herbarium code used to identify it.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb9d11f081909fc51e84657ec7f1 |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.