Triple
T36743092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Thames between Staines and Egham |
E907674
|
entity |
| Predicate | nonTidal |
P74730
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [River Thames between Staines and Egham, nonTidal, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonTidal Context triple: [River Thames between Staines and Egham, nonTidal, true]
-
A.
isNonTidal
chosen
Indicates that the body of water or water level is not significantly affected by tidal forces or tidal cycles.
-
B.
notTributaryOf
Indicates that one watercourse or river is explicitly not a tributary of another watercourse or river.
-
C.
nonVocal
Indicates that the subject does not produce vocal sounds or speech in the context of the described action or state.
-
D.
neverDrained
Indicates that the entity has not been emptied, exhausted, or depleted at any time in the relevant context or period.
-
E.
nonperturbativeIn
Indicates that something occurs, is treated, or is valid in a nonperturbative regime or framework within a specified context or system.
- 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_69f76e76d10881909ec1679bc043108c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.