Triple
T7189583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arctic tern |
E167652
|
entity |
| Predicate | defenseBehavior |
P26653
|
FINISHED |
| Object | aggressively defends nest |
—
|
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: aggressively defends nest | Statement: [Arctic tern, defenseBehavior, aggressively defends nest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defenseBehavior Context triple: [Arctic tern, defenseBehavior, aggressively defends nest]
-
A.
defenseResult
Indicates the outcome or consequence of a defensive action or strategy in response to an attack or threat.
-
B.
defense
Indicates an action or relationship in which an entity protects, guards, or resists against a threat, attack, or criticism from another entity.
-
C.
antiPredatorStrategy
chosen
Indicates a behavior or adaptation used to avoid, deter, or reduce the risk of predation by other organisms.
-
D.
defends
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
E.
defenseArgument
Indicates that an entity presents or supports a line of reasoning intended to defend or justify another entity, often in a legal or argumentative 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e8ff1ad0819094761f8c73e3e986 |
completed | March 27, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:50 p.m.