Triple
T36054645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parselmouths |
E1042909
|
entity |
| Predicate | speciesCommunicatedWith |
P184627
|
FINISHED |
| Object | snakes |
—
|
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: snakes | Statement: [Parselmouths, speciesCommunicatedWith, snakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speciesCommunicatedWith Context triple: [Parselmouths, speciesCommunicatedWith, snakes]
-
A.
speciesAssociatedWith
chosen
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.
-
B.
guestSpecies
Indicates a relationship where one species is present as a guest or non-native participant within the context or environment of another.
-
C.
speciesType
Indicates the specific biological species category to which an entity belongs.
-
D.
hostSpecies
Indicates the species that serves as the host for another organism, agent, or entity.
-
E.
forSpecies
Indicates that something is intended for, associated with, or applicable to a particular 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 3, 2026, 4:08 p.m.