Triple
T24150958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack |
E598530
|
entity |
| Predicate | languageOfScientificNameAbbreviation |
P87409
|
FINISHED |
| Object | Latin |
—
|
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: Latin | Statement: [Jack, languageOfScientificNameAbbreviation, Latin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfScientificNameAbbreviation Context triple: [Jack, languageOfScientificNameAbbreviation, Latin]
-
A.
scientificNameAbbreviation
Indicates that one entity is an abbreviated or shortened form of the scientific name of another entity.
-
B.
taxonAbbreviation
Indicates that one taxonomic entity is associated with a standardized abbreviated form of its scientific name.
-
C.
binomialNomenclatureLanguage
chosen
Indicates the language in which a taxon's binomial (scientific) name is expressed.
-
D.
scientificName
Indicates the formal taxonomic name assigned to an organism according to scientific naming conventions.
-
E.
hasScientificDesignation
Indicates that an entity is associated with a specific formal scientific name or designation used in scientific classification or nomenclature.
- 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e0e108308190ba8740590a1c5130 |
completed | April 29, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:30 p.m.