Triple
T19698360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goldone |
E473024
|
entity |
| Predicate | tributaryBank |
P136971
|
FINISHED |
| Object | left |
—
|
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: left | Statement: [Goldone, tributaryBank, left]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tributaryBank Context triple: [Goldone, tributaryBank, left]
-
A.
riverBankOne
Indicates that the referenced entity is one specific side or bank of a river, typically the first or primary one in a pairwise relation.
-
B.
denominationBranch
Indicates that one religious organization or group is a subordinate branch, division, or subset of a larger religious denomination.
-
C.
servesBank
Indicates that one entity provides banking or financial services to another entity.
-
D.
riverBankTwo
Indicates a relationship where something is located on or associated with the second of two identified banks of a river.
-
E.
connectsBank
Indicates a relationship where one entity serves to link or provide access between another entity and a bank or banking service.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b2baec81909ee2cd6ead632836 |
completed | April 20, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
| PDg | Predicate description generation | batch_69e532bbedf081908d801600e2af94a7 |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:46 p.m.