Triple
T28373220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The English Review |
E718688
|
entity |
| Predicate | successorEditorToFordMadoxFord |
P193183
|
FINISHED |
| Object | Austin Harrison |
E1815659
|
NE 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: Austin Harrison | Statement: [The English Review, successorEditorToFordMadoxFord, Austin Harrison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorEditorToFordMadoxFord Context triple: [The English Review, successorEditorToFordMadoxFord, Austin Harrison]
-
A.
successorManufacturer
Indicates that one manufacturer has taken over, replaced, or continued the role or operations of another manufacturer as its successor.
-
B.
formerManufacturer
Indicates that an entity previously manufactured another entity but no longer does so.
-
C.
successorEngine
Indicates that one engine directly follows and replaces another in a sequence or version lineage.
-
D.
successorEngineFamily
Indicates that one engine family directly follows and replaces another in a product or development lineage.
-
E.
yearFordProductionMovedOut
Indicates the year in which Ford’s production operations were relocated away from a particular place.
- F. None of above. chosen
Provenance (5 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a1cac305368819092525d1337354360 |
completed | May 31, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
| PDg | Predicate description generation | batch_69fd3a6905b88190ae12b43576f4cc63 |
completed | May 8, 2026, 1:20 a.m. |
Created at: April 28, 2026, 1:01 a.m.