Triple
T30750306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guanshan biota |
E782937
|
entity |
| Predicate | hasLanguageOfScientificDescription |
P108236
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Guanshan biota, hasLanguageOfScientificDescription, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOfScientificDescription Context triple: [Guanshan biota, hasLanguageOfScientificDescription, English]
-
A.
hasMorphologyDescribedIn
Indicates that the morphology of an entity is documented or characterized in a specified source or description.
-
B.
hasScientificDesignation
Indicates that an entity is associated with a specific formal scientific name or designation used in scientific classification or nomenclature.
-
C.
hasScientificSpecies
Indicates that an entity is associated with a specific scientific (Latin) species name.
-
D.
hasTaxonomicDescriptions
Indicates that an entity is associated with one or more formal taxonomic descriptions that define or characterize its classification.
-
E.
languageOfOriginalDescription
chosen
Indicates that something is expressed or documented in its initial or source language version.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdd92396788190ae1424bc1ae55844 |
completed | May 8, 2026, 12:37 p.m. |
| PD | Predicate disambiguation | batch_69fdd678f40481909a717a2daec83b36 |
completed | May 8, 2026, 12:26 p.m. |
Created at: April 29, 2026, 8:38 p.m.