Triple
T11071182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quezon Bridge |
E261748
|
entity |
| Predicate | connectsBankOfRiver |
P73938
|
FINISHED |
| Object | north bank of Pasig River |
—
|
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: north bank of Pasig River | Statement: [Quezon Bridge, connectsBankOfRiver, north bank of Pasig River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsBankOfRiver Context triple: [Quezon Bridge, connectsBankOfRiver, north bank of Pasig River]
-
A.
connectsBank
Indicates a relationship where one entity serves to link or provide access between another entity and a bank or banking service.
-
B.
riverBankOnEastSide
Indicates that a river bank is located on the eastern side of a river or watercourse.
-
C.
locatedOnBankOfRiver
Indicates that one entity is situated along or directly adjacent to the bank of a specified river.
-
D.
crossRiverLink
chosen
Indicates a connection or route that enables passage across a river between two locations.
-
E.
hasBank
Indicates that one entity possesses, is associated with, or is served by a particular bank (such as a financial institution or river bank).
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7994bbb30819090410bd3d0fde33c |
completed | April 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.