Triple
T10107098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cynomys |
E216346
|
entity |
| Predicate | notedInResearchFor |
P46827
|
FINISHED |
| Object | animal communication |
—
|
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: animal communication | Statement: [Cynomys, notedInResearchFor, animal communication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notedInResearchFor Context triple: [Cynomys, notedInResearchFor, animal communication]
-
A.
notedIn
Indicates that information about one entity is mentioned, recorded, or referenced within another entity, such as a document, record, or source.
-
B.
hasScientificInterestIn
Indicates that one entity holds a scientific curiosity, concern, or research focus directed toward another entity.
-
C.
notableExperiment
Indicates that an entity is recognized for having conducted or been the subject of a particularly important or influential experiment.
-
D.
appliesResearchTo
Indicates that an entity uses or implements research findings, methods, or insights in relation to another entity, context, or problem.
-
E.
widelyStudiedIn
chosen
Indicates that something has been extensively researched, analyzed, or examined within a particular field, domain, or context.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd0ca7f7c8190ba7ed37940aa933d |
completed | April 2, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:03 p.m.