Triple
T37540373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abathur |
E933310
|
entity |
| Predicate | functionInSwarm |
P188711
|
FINISHED |
| Object | Adaptation of Zerg to enemies |
—
|
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: Adaptation of Zerg to enemies | Statement: [Abathur, functionInSwarm, Adaptation of Zerg to enemies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: functionInSwarm Context triple: [Abathur, functionInSwarm, Adaptation of Zerg to enemies]
-
A.
functionInWork
Indicates that a particular function, role, or operation is performed, utilized, or occurs within the context of a specific work or creation.
-
B.
functionInSystem
Indicates that an entity serves a specific role or performs a particular function within a given system.
-
C.
functionInPractice
Indicates that an entity serves a particular role or performs a specific function in actual use or real-world practice.
-
D.
functionInCitadel
Indicates that an entity serves a specific role or performs a particular function within a citadel.
-
E.
junctionFunction
Indicates a functional relationship where one entity serves as a junction or connection point integrating or routing flows, signals, or interactions between multiple other entities.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbacaea12c8190a4c99e64335f0e7e |
completed | May 6, 2026, 9:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.