Triple
T26868554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grallariidae |
E676540
|
entity |
| Predicate | associatedBehavior |
P23475
|
FINISHED |
| Object | skulking in dense vegetation |
—
|
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: skulking in dense vegetation | Statement: [Grallariidae, associatedBehavior, skulking in dense vegetation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedBehavior Context triple: [Grallariidae, associatedBehavior, skulking in dense vegetation]
-
A.
affectsBehaviorOf
Indicates that one entity produces a change or influence on the behavior, actions, or conduct of another entity.
-
B.
privateBehavior
Indicates behavior or actions that are intended to be kept confidential, hidden, or restricted from public or general observation.
-
C.
behaviorObserved
chosen
Indicates that a particular behavior or action has been witnessed, recorded, or detected in relation to an entity or context.
-
D.
associated act
Indicates a relationship where one act is connected or linked to another act, typically as a related or accompanying action.
-
E.
behaviorNear
Indicates that one entity exhibits a behavior or action in close spatial proximity to another entity.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
Created at: April 27, 2026, 5:30 a.m.