Triple
T31553318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bleeker, 1863 |
E805061
|
entity |
| Predicate | appliesToFamilyCommonName |
P61588
|
FINISHED |
| Object | bitterlings |
—
|
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: bitterlings | Statement: [Bleeker, 1863, appliesToFamilyCommonName, bitterlings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToFamilyCommonName Context triple: [Bleeker, 1863, appliesToFamilyCommonName, bitterlings]
-
A.
belongsToFamilyCommonName
chosen
Indicates that an entity is associated with, or classified under, a particular family-level common name.
-
B.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as another entity.
-
C.
includesCommonName
Indicates that one entity contains or specifies a commonly used (non-scientific) name for another entity.
-
D.
appliesToLanguageFamily
Indicates that something (such as a rule, feature, or classification) is relevant or applicable to an entire language family rather than to a single language.
-
E.
containsFamily
Indicates that one entity includes or encompasses members of a particular family group within 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: April 30, 2026, 10:12 p.m.