Triple
T16012163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Spikes |
E388364
|
entity |
| Predicate | hasBiologicalWeakness |
P583
|
FINISHED |
| Object | vulnerable to cold |
—
|
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: vulnerable to cold | Statement: [White Spikes, hasBiologicalWeakness, vulnerable to cold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBiologicalWeakness Context triple: [White Spikes, hasBiologicalWeakness, vulnerable to cold]
-
A.
hasWeakness
Indicates that one entity is vulnerable to, or can be adversely affected or defeated by, another entity.
-
B.
effectivenessAgainst
Indicates how well one entity performs in countering, influencing, or mitigating the impact of another entity.
-
C.
biologicalCharacteristic
Indicates that one entity possesses or exhibits a particular biological trait, feature, or property in relation to another.
-
D.
susceptibleTo
chosen
Indicates that one entity is vulnerable or likely to be affected, harmed, or influenced by another entity or factor.
-
E.
isResistant
Indicates that an entity can withstand, oppose, or is not significantly affected by a specified force, influence, or agent.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e1826a4f7c8190aba6d4f1075141b0 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:55 a.m.