Triple
T31515539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Owen Warland |
E804063
|
entity |
| Predicate | isIsolatedBy |
P39640
|
FINISHED |
| Object | his artistic obsession |
—
|
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: his artistic obsession | Statement: [Owen Warland, isIsolatedBy, his artistic obsession]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isIsolatedBy Context triple: [Owen Warland, isIsolatedBy, his artistic obsession]
-
A.
isIsolated
Indicates that an entity exists or occurs separately from others, without direct contact, interaction, or connection.
-
B.
isolatedBy
chosen
Indicates that one entity has been separated or kept apart from another entity or set of entities, preventing interaction or influence between them.
-
C.
hasRelativeIsolation
Indicates that one entity exists in a state of separation or limited interaction relative to another entity or its surroundings.
-
D.
hasIsolation
Indicates that an entity is separated or kept apart from others, typically to prevent interaction, influence, or contamination.
-
E.
isolateFrom
Indicates that one entity is separated or kept apart from another entity or source.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a2578cb081908304c8d338fb5b81 |
completed | May 3, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:52 p.m.