Triple
T31953534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sokovian |
E815843
|
entity |
| Predicate | affectedByOrganization |
P179953
|
FINISHED |
| Object | HYDRA |
—
|
NE NERFINISHED |
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: HYDRA | Statement: [Sokovian, affectedByOrganization, HYDRA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedByOrganization Context triple: [Sokovian, affectedByOrganization, HYDRA]
-
A.
endedOrganization
Indicates that an organization has ceased to exist or operate, marking the termination of its existence or activities.
-
B.
includesOrganization
Indicates that one entity contains, encompasses, or has within it the specified organization as a component, member, or part.
-
C.
usesOrganization
Indicates that one entity makes use of, relies on, or operates through a particular organization to perform its functions or activities.
-
D.
allyOrganization
Indicates that one organization has a cooperative or supportive alliance relationship with another organization.
-
E.
connectedOrganization
Indicates that there is an established relationship or association between two organizations, such that one is linked or affiliated with the other in some relevant context.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
| PDg | Predicate description generation | batch_69f72920c6208190aa4aba6cb6193109 |
completed | May 3, 2026, 10:53 a.m. |
Created at: May 1, 2026, 12:08 a.m.