Triple
T1772224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odocoileus virginianus |
E38899
|
entity |
| Predicate | alarmSignal |
P31706
|
FINISHED |
| Object | tail-flagging with white tail raised |
—
|
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: tail-flagging with white tail raised | Statement: [Odocoileus virginianus, alarmSignal, tail-flagging with white tail raised]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alarmSignal Context triple: [Odocoileus virginianus, alarmSignal, tail-flagging with white tail raised]
-
A.
alertSystem
Indicates that a system is configured to detect conditions and generate alerts or notifications in response.
-
B.
alertMethod
Indicates the method or channel through which an alert or notification is delivered from a source to a recipient.
-
C.
civilSignal
Indicates a formal, non-criminal legal communication or notice issued between parties within a civil law context.
-
D.
bellPattern
Indicates that one entity exhibits or follows a bell-shaped or bell-like pattern in relation to another entity or variable.
-
E.
numberOfBells
Indicates the quantity of bells associated with or present in a given entity or context.
- F. None of above. chosen
Provenance (4 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab39fc2c448190bfaf1ee8d474632a |
completed | March 6, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69aa61cbb1288190a7ba38b61905f578 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab39faf69c8190bae98d3e3911078f |
completed | March 6, 2026, 8:32 p.m. |
Created at: March 4, 2026, 7:31 p.m.