Triple
T18206618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helmholtz Watson |
E435917
|
entity |
| Predicate | attitudeTowardExile |
P59360
|
FINISHED |
| Object | Accepts exile positively |
—
|
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: Accepts exile positively | Statement: [Helmholtz Watson, attitudeTowardExile, Accepts exile positively]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attitudeTowardExile Context triple: [Helmholtz Watson, attitudeTowardExile, Accepts exile positively]
-
A.
emotionOnLearningOfExile
chosen
Indicates the emotional response an entity experiences upon learning that they or another entity has been exiled.
-
B.
statusAfterExile
Indicates the condition or standing an entity has once a period of exile has ended.
-
C.
exileCountry
Indicates that an entity has been banished from or forced to live outside a specified country.
-
D.
traditionallyExiledTo
Indicates that an entity has, by long-standing custom or tradition, been sent away or banished to a particular place.
-
E.
causeOfExile
Indicates the reason or circumstance that led to an entity’s exile.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e2243de081908a5bcc7e2072eae7 |
completed | April 19, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.