Triple
T20233757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Macaulay Booth |
E495595
|
entity |
| Predicate | supportedWorkOn |
P33893
|
FINISHED |
| Object | poverty in London |
—
|
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: poverty in London | Statement: [Mary Macaulay Booth, supportedWorkOn, poverty in London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedWorkOn Context triple: [Mary Macaulay Booth, supportedWorkOn, poverty in London]
-
A.
supportedByWork
Indicates that one entity’s existence, validity, or outcome is backed, justified, or enabled by the work or efforts of another entity.
-
B.
supportedWork
chosen
Indicates that one entity provides assistance, resources, or endorsement to enable or sustain the work or activity of another entity.
-
C.
supportingWork
Indicates that one work provides assistance, reinforcement, or supplementary value to another work, helping to sustain or enhance it.
-
D.
respondsToWork
Indicates that one entity replies or reacts to another entity’s work, output, or contribution.
-
E.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e67167fae88190a26ff10d698174f8 |
completed | April 20, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:40 p.m.