Triple
T2048563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tragulidae |
E45509
|
entity |
| Predicate | escapeBehavior |
P35560
|
FINISHED |
| Object | rapid dashing into dense cover |
—
|
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: rapid dashing into dense cover | Statement: [Tragulidae, escapeBehavior, rapid dashing into dense cover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: escapeBehavior Context triple: [Tragulidae, escapeBehavior, rapid dashing into dense cover]
-
A.
limitBehavior
Indicates how an entity behaves or changes as it approaches a specified limit or boundary condition.
-
B.
defaultBehavior
Indicates the standard or fallback way an entity acts or responds when no specific or overriding instructions or conditions are provided.
-
C.
throws
Indicates that one entity propels or hurls another entity or object through space, typically by a deliberate physical action.
-
D.
behaviorNear
Indicates that one entity exhibits a behavior or action in close spatial proximity to another entity.
-
E.
designedToAvoid
Indicates that something was intentionally created or configured in a way that prevents or minimizes a particular outcome, condition, or interaction.
- 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_69a8891948208190ab7898da21824c77 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb98c70c48190beb98aad56d9daf1 |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7abba508190b872f345d3ba51bb |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb94ec400819097596732aabed854 |
completed | March 7, 2026, 5:36 a.m. |
Created at: March 4, 2026, 7:39 p.m.