Triple
T27712002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lakes Aquarium (at Lakeside) |
E698714
|
entity |
| Predicate | hasSpeciesScope |
P397
|
FINISHED |
| Object | regional aquatic species |
—
|
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: regional aquatic species | Statement: [Lakes Aquarium (at Lakeside), hasSpeciesScope, regional aquatic species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeciesScope Context triple: [Lakes Aquarium (at Lakeside), hasSpeciesScope, regional aquatic species]
-
A.
hasSpeciesRole
Indicates that an entity plays a specific functional or categorical role within a particular species.
-
B.
hasScope
chosen
Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
-
C.
hasOnlySpecies
Indicates that an entity is associated exclusively with a single specified species and no others.
-
D.
includesSpeciesFrom
Indicates that one collection, group, or set contains one or more species that originate from or belong to another specified source or context.
-
E.
includesSpecies
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 27, 2026, 3:02 p.m.