Triple
T21621050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fore Abbey |
E533576
|
entity |
| Predicate | associatedWonder |
P144811
|
FINISHED |
| Object | the water that flows uphill |
—
|
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: the water that flows uphill | Statement: [Fore Abbey, associatedWonder, the water that flows uphill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWonder Context triple: [Fore Abbey, associatedWonder, the water that flows uphill]
-
A.
questHubFor
Indicates a relationship where one entity serves as the central location or main coordination point for quests associated with another entity.
-
B.
explores
Indicates actively investigating, traveling through, or examining something in order to discover or learn more about it.
-
C.
associatedMystic
Indicates a relationship where one entity is linked or connected to another through a mystical, spiritual, or esoteric association.
-
D.
questedBy
Indicates that a quest or mission is initiated, assigned, or undertaken by a particular entity.
-
E.
alsoFeatured
Indicates that an entity appears in addition to another primary entity within the same context, work, or presentation.
- F. None of above. chosen
Provenance (4 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3bafef548190b3856bfad1ebdc0b |
completed | April 27, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:34 p.m.