Triple
T24699732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea Lion Stadium |
E611697
|
entity |
| Predicate | featuresAnimalSpecies |
P7733
|
FINISHED |
| Object | California sea lion |
—
|
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: California sea lion | Statement: [Sea Lion Stadium, featuresAnimalSpecies, California sea lion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresAnimalSpecies Context triple: [Sea Lion Stadium, featuresAnimalSpecies, California sea lion]
-
A.
featuresSpecies
chosen
Indicates that something includes, presents, or highlights a particular species as part of its content or composition.
-
B.
featuresAnimalsFrom
Indicates that one entity includes, presents, or showcases animals originating from or associated with another entity.
-
C.
animalScientificNameFeatured
Indicates that a particular scientific (taxonomic) name of an animal is highlighted or designated as the primary/featured name in a given context.
-
D.
speciesHome
Indicates that a particular location serves as the natural habitat or primary living environment for a given species.
-
E.
animalForm
Indicates that one entity takes the shape, body, or characteristics of an animal.
- 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 3:22 a.m.