Triple
T38561034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tetanus |
E928075
|
entity |
| Predicate | isNotEradicableByHumanToHumanControl |
P191194
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [tetanus, isNotEradicableByHumanToHumanControl, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotEradicableByHumanToHumanControl Context triple: [tetanus, isNotEradicableByHumanToHumanControl, true]
-
A.
cannotBeEasilyDisabled
Indicates that the relationship or mechanism cannot be turned off, bypassed, or neutralized without significant effort, expertise, or resources.
-
B.
cannotDieInHumanSense
Indicates that the entity is not subject to death or mortality in the way humans experience or understand it.
-
C.
speciesControlled
Indicates that one entity exerts control, management, or regulatory influence over a particular species.
-
D.
cannotBeReliablyCultivated
Indicates that the entity cannot be consistently or predictably grown or produced under controlled or managed conditions.
-
E.
isUnderControlOf
Indicates that one entity is subject to the authority, direction, or governance of another entity.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdaa2bfc08190beccabb0f1782d0d |
completed | May 7, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:32 p.m.