Triple
T35832362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ural owl |
E1035831
|
entity |
| Predicate | aggression |
P101476
|
FINISHED |
| Object | can aggressively defend 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: can aggressively defend nest | Statement: [Ural owl, aggression, can aggressively defend nest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aggression Context triple: [Ural owl, aggression, can aggressively defend nest]
-
A.
aggressiveness
chosen
Indicates a tendency or disposition of an entity to initiate hostile, forceful, or confrontational actions toward others.
-
B.
describesAggressionAs
Indicates how one entity characterizes or portrays the aggression exhibited by another entity.
-
C.
offense
Indicates that one entity commits, causes, or is responsible for a violation, wrongdoing, or rule-breaking act against another entity or governing norms.
-
D.
attacks
Indicates that one entity initiates an aggressive or harmful action directed toward another entity.
-
E.
offenseAgainst
Indicates that one party has committed a harmful, illegal, or rule-violating act directed against another party or 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_69f76e192a94819082db360cb91e6a8d |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.