Triple
T35087153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | States Parties to the Biological Weapons Convention |
E1012606
|
entity |
| Predicate | hasStatusType |
P96867
|
FINISHED |
| Object | ratification |
—
|
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: ratification | Statement: [States Parties to the Biological Weapons Convention, hasStatusType, ratification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatusType Context triple: [States Parties to the Biological Weapons Convention, hasStatusType, ratification]
-
A.
hasStatusBasedOn
Indicates that an entity’s status is determined or derived from another condition, event, or entity.
-
B.
hasStatusIn
Indicates that an entity holds or is assigned a particular status within a specified context, scope, or system.
-
C.
typeOfStatus
chosen
Indicates the specific status category or condition that an entity is classified as having.
-
D.
isStatusOf
Indicates that a particular status or condition is assigned to, or characterizes, a specific entity.
-
E.
hasStatusLabel
Indicates that an entity is associated with a specific status expressed as a human-readable label.
- 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_69f76dd432ec8190969bc32acfc152b1 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffcb5536d88190bfc2e00b854cacfb |
completed | May 10, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69ffc900c2a081909dea04aa60566923 |
completed | May 9, 2026, 11:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.