Triple
T620782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vespidae |
E14506
|
entity |
| Predicate | venomFunction |
P17207
|
FINISHED |
| Object | defense |
—
|
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: defense | Statement: [Vespidae, venomFunction, defense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: venomFunction Context triple: [Vespidae, venomFunction, defense]
-
A.
possibleFunction
Indicates that an entity may serve, or is capable of serving, a particular function or role, without asserting that it actually does so.
-
B.
intendedFunction
Indicates that something is designed or purposed to perform a particular role, use, or function.
-
C.
HydraFunction
Indicates a function or operation that, when invoked, can produce multiple concurrent or branching outcomes or processes from a single initiating action.
-
D.
attackToolExample
Indicates that a specific tool or method is used as an example of how an attack is or can be carried out.
-
E.
windmillFunction
Indicates that something serves as or performs the function of a windmill, typically converting wind energy into mechanical or electrical power.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e3e5d80819096e72e11b533f931 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49cfe9bc081909a01b4b3b48f03b7 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49defe58c8190bd39ef47c9f660a7 |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.