Triple
T35571142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elizabeth Lyttleton Harold |
E1027938
|
entity |
| Predicate | assistedWorkOf |
P104801
|
FINISHED |
| Object | Alan Lomax |
—
|
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: Alan Lomax | Statement: [Elizabeth Lyttleton Harold, assistedWorkOf, Alan Lomax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assistedWorkOf Context triple: [Elizabeth Lyttleton Harold, assistedWorkOf, Alan Lomax]
-
A.
supportingWork
Indicates that one work provides assistance, reinforcement, or supplementary value to another work, helping to sustain or enhance it.
-
B.
wasAssistedBy
Indicates that an entity carried out an action or achieved a result with the help or support of another entity.
-
C.
workWith
Indicates that one entity collaborates or engages in work-related activities together with another entity.
-
D.
contributionToWork
chosen
Indicates a relationship where an entity has provided effort, input, or resources that help create, develop, or complete a particular work.
-
E.
assistance
Indicates providing help, support, or aid from one entity to another to facilitate a task, goal, or need.
- 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_69f76e0386688190b931bacdc145938c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.