Triple
T36958193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arachnotron |
E914240
|
entity |
| Predicate | hasWeakPoint |
P47330
|
FINISHED |
| Object | brain |
—
|
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: brain | Statement: [Arachnotron, hasWeakPoint, brain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWeakPoint Context triple: [Arachnotron, hasWeakPoint, brain]
-
A.
hasWeakness
chosen
Indicates that one entity is vulnerable to, or can be adversely affected or defeated by, another entity.
-
B.
initialWeakness
Indicates that an entity has a vulnerability or disadvantage present at the beginning of a process, event, or interaction.
-
C.
branchWeakened
Indicates that a branch has lost strength or stability, becoming structurally weaker than before.
-
D.
hasNotableStrengthIn
Indicates that an entity possesses a particularly high level of ability, effectiveness, or advantage in a specific area or domain.
-
E.
hasBaseDefense
Indicates that an entity possesses a specified level or value of defensive capability in its default or starting state.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:13 p.m.