Triple
T15638488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Bath |
E376004
|
entity |
| Predicate | drainageLeadsTo |
P81003
|
FINISHED |
| Object | nearby drain or well |
—
|
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: nearby drain or well | Statement: [Great Bath, drainageLeadsTo, nearby drain or well]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drainageLeadsTo Context triple: [Great Bath, drainageLeadsTo, nearby drain or well]
-
A.
causeOfDrainage
Indicates the factor or process that leads to or is responsible for the drainage of a substance, area, or system.
-
B.
drainageBetween
Indicates that one area or feature serves as a drainage path or channel between two other areas or features, allowing water or runoff to flow from one to the other.
-
C.
drainageType
Indicates the kind or classification of drainage associated with or applied to an entity (e.g., how water is removed or flows from it).
-
D.
drainageOutlet
chosen
Indicates that one entity serves as the point where fluids or runoff are discharged or exit from another entity.
-
E.
drainageInfluencedBy
Indicates that the pattern, direction, or effectiveness of drainage is affected or controlled by another factor or 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eba51f08190ac5d9de7fc89405a |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.