Triple
T30958941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bar-ba-loots |
E788754
|
entity |
| Predicate | relatedSpeciesInStory |
P207330
|
FINISHED |
| Object | Swomee-Swans |
E788755
|
NE 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: Swomee-Swans | Statement: [Bar-ba-loots, relatedSpeciesInStory, Swomee-Swans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedSpeciesInStory Context triple: [Bar-ba-loots, relatedSpeciesInStory, Swomee-Swans]
-
A.
relatedSpeciesOrVariant
Indicates that one species or biological variant is taxonomically or genetically related to another.
-
B.
relatedWildSpecies
Indicates a relationship where one entity is a wild species that is taxonomically or ecologically related to another entity.
-
C.
associatedCharacterSpecies
Indicates that one entity is related to, or linked with, the species of a particular character.
-
D.
speciesAssociatedWith
Indicates that there is a relevant connection or linkage between a species and another entity (such as a habitat, condition, or feature), without specifying the exact nature of that relationship.
-
E.
associatedBeings
Indicates that two or more beings are linked or connected to each other in some relevant way.
- F. None of above. chosen
Provenance (5 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a28fbb1153c819092487a6e0be842c0 |
completed | June 10, 2026, 5:52 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 8:54 p.m.