Triple
T1036602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vivienne Haigh-Wood Eliot |
E22376
|
entity |
| Predicate | roleInTSEliotLife |
P24214
|
FINISHED |
| Object | muse-like influence |
—
|
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: muse-like influence | Statement: [Vivienne Haigh-Wood Eliot, roleInTSEliotLife, muse-like influence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTSEliotLife Context triple: [Vivienne Haigh-Wood Eliot, roleInTSEliotLife, muse-like influence]
-
A.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
B.
roleInCommunity
Indicates the function, position, or set of responsibilities an entity holds within a particular community or group.
-
C.
roleInEcosystem
Indicates the specific function or contribution an entity has within an ecosystem and how it interacts with other components of that system.
-
D.
roleInCouncil
Indicates that an entity holds a specific position or function within a council or governing body.
-
E.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
- 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_69a493d848848190aed4011b34b2e8d3 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b97c64a88190bf1119fdd4940bf3 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b729f8488190b2042bd9c625a833 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b97acbf4819087b92a8b29baef46 |
completed | March 1, 2026, 10:11 p.m. |
Created at: March 1, 2026, 7:41 p.m.