Triple
T37061552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 琵琶湖 |
E917336
|
entity |
| Predicate | 代表的な固有種 |
P174009
|
FINISHED |
| Object | ビワコオオナマズ |
—
|
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: ビワコオオナマズ | Statement: [琵琶湖, 代表的な固有種, ビワコオオナマズ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 代表的な固有種 Context triple: [琵琶湖, 代表的な固有種, ビワコオオナマズ]
-
A.
isRepresentativeVarietyOf
chosen
Indicates that one entity serves as a typical or standard example representing the broader characteristics of another entity or group.
-
B.
scientificNameOfRepresentativeSpecies
Indicates that one entity is the scientific (Latin) name corresponding to the representative species of another entity (such as a group, category, or taxon).
-
C.
hasSolitarySpecies
Indicates that an entity includes or is associated with species that live or behave predominantly alone rather than in groups.
-
D.
hasNotableSpecimen
Indicates that an entity possesses or is associated with a specimen that is considered particularly significant, remarkable, or noteworthy.
-
E.
monotypicTaxon
Indicates that a taxonomic group contains only a single subordinate taxon (e.g., a genus with only one species).
- 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.