Triple
T28031574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deep Blue Sea 2 |
E708281
|
entity |
| Predicate | hasSpeciesFeatured |
P7733
|
FINISHED |
| Object | shark |
—
|
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: shark | Statement: [Deep Blue Sea 2, hasSpeciesFeatured, shark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeciesFeatured Context triple: [Deep Blue Sea 2, hasSpeciesFeatured, shark]
-
A.
hasFlagshipSpecies
Indicates that one entity (typically a site, region, or conservation program) is associated with or represented by a particular flagship species used to promote awareness or protection.
-
B.
hasExhibitSpecies
Indicates that an exhibit or display includes or features a particular species.
-
C.
featuresSpecies
chosen
Indicates that something includes, presents, or highlights a particular species as part of its content or composition.
-
D.
hasNotableSpecimen
Indicates that an entity possesses or is associated with a specimen that is considered particularly significant, remarkable, or noteworthy.
-
E.
hasScientificSpecies
Indicates that an entity is associated with a specific scientific (Latin) species name.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 27, 2026, 8:17 p.m.