Triple
T9357754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chapter IV: The Supper-Table |
E225185
|
entity |
| Predicate | followsInWork |
P9710
|
FINISHED |
| Object | Chapter III of The Blithedale Romance |
—
|
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: Chapter III of The Blithedale Romance | Statement: [Chapter IV: The Supper-Table, followsInWork, Chapter III of The Blithedale Romance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsInWork Context triple: [Chapter IV: The Supper-Table, followsInWork, Chapter III of The Blithedale Romance]
-
A.
followsWork
chosen
Indicates that one work (such as a publication, version, or creative piece) comes directly after another in sequence or succession.
-
B.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
C.
follows
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
-
D.
followsBetween
Indicates that one entity comes after or succeeds another entity within a specified context or sequence.
-
E.
followedIn
Indicates that one entity began following or subscribing to another entity, typically in a social or sequential context.
- 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_69ca842bdd648190904131d58620d448 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4ff06608819086e9f11789beaf22 |
completed | April 1, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69cc7a68ab9481909f97cb70764697cc |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:42 p.m.