Triple
T30466531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ties That Bind: The River Collection |
E775156
|
entity |
| Predicate | mainWorkCenteredOn |
P16614
|
FINISHED |
| Object | The River |
—
|
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: The River | Statement: [The Ties That Bind: The River Collection, mainWorkCenteredOn, The River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainWorkCenteredOn Context triple: [The Ties That Bind: The River Collection, mainWorkCenteredOn, The River]
-
A.
centralWork
chosen
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
B.
developmentCenteredOn
Indicates that the primary focus or core activity of a development process, project, or initiative is oriented around a particular entity or aspect.
-
C.
mainWorkSite
Indicates the primary location or site where an entity mainly performs its work or operations.
-
D.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
E.
formsCenterOf
Indicates that one entity constitutes the central or core part of another entity.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686f3c8348190b5fea0c6fbeae253 |
completed | May 2, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69f678d2196c8190b9d0d2fcd47cc539 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:11 p.m.