Triple
T16855196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apis florea |
E409763
|
entity |
| Predicate | nestDefense |
P6876
|
FINISHED |
| Object | shimmering behavior |
—
|
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: shimmering behavior | Statement: [Apis florea, nestDefense, shimmering behavior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nestDefense Context triple: [Apis florea, nestDefense, shimmering behavior]
-
A.
defensiveSystem
Indicates a system or mechanism whose primary function is to protect, guard, or defend an entity against threats or attacks.
-
B.
defenseLayer
Indicates a protective barrier or mechanism that shields an entity from harm, attack, or unwanted influence.
-
C.
defenderIn
Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
-
D.
defends
chosen
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
E.
defenseControl
Indicates that one entity exercises authority over, manages, or directs the defensive capabilities or protective measures of 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b37c6e808190975b14b228253029 |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.