Triple
T24316864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vasco da Gama Tower |
E612844
|
entity |
| Predicate | riverPanorama |
P155526
|
FINISHED |
| Object | Tagus estuary |
—
|
NE NERFINISHED |
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: Tagus estuary | Statement: [Vasco da Gama Tower, riverPanorama, Tagus estuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverPanorama Context triple: [Vasco da Gama Tower, riverPanorama, Tagus estuary]
-
A.
riverPhenomenon
Indicates a natural event, condition, or process that occurs in or directly affects a river.
-
B.
riverFeatureType
Indicates the specific kind or category of physical or functional feature associated with a river (e.g., source, mouth, tributary, channel segment).
-
C.
parallelWaterway
Indicates that one waterway runs alongside another waterway in a roughly parallel course without significantly intersecting it.
-
D.
waterwayThrough
Indicates that a waterway (such as a river or canal) passes through or traverses a specified geographic area or feature.
-
E.
riverExplored
Indicates that an entity has been explored or surveyed along the course of a river.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292a834148190ab084c11cb3e59fe |
completed | April 29, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 1:47 a.m.