Triple
T18848282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fertagus cross-Tagus rail |
E460973
|
entity |
| Predicate | connectsSide |
P845
|
FINISHED |
| Object | north bank of Tagus 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 Tagus River | Statement: [Fertagus cross-Tagus rail, connectsSide, north bank of Tagus River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsSide Context triple: [Fertagus cross-Tagus rail, connectsSide, north bank of Tagus River]
-
A.
connectsPartOf
Indicates a relationship where one entity serves to link or join a component to the larger whole of which that component is a part.
-
B.
connectsUnder
Indicates that one entity forms a connection to another entity by passing beneath or under it.
-
C.
connectsSystem
Indicates that one system establishes a link or interface with another system, enabling interaction or data exchange between them.
-
D.
connectsTo
chosen
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
E.
connectsWorks
Indicates a relationship where one work serves to link, bridge, or associate two or more other works.
- 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_69d8dcfa11e4819090ab1ef5bdcd2b2e |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5b8f079b881908759135c5e2619ee |
completed | April 20, 2026, 5:26 a.m. |
| PD | Predicate disambiguation | batch_69e48d1e7dac81909ea1e758c87773c5 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:56 a.m.