Triple
T8434581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tis Issat |
E199193
|
entity |
| Predicate | viewingPoints |
P17987
|
FINISHED |
| Object | multiple viewpoints along both banks |
—
|
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: multiple viewpoints along both banks | Statement: [Tis Issat, viewingPoints, multiple viewpoints along both banks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewingPoints Context triple: [Tis Issat, viewingPoints, multiple viewpoints along both banks]
-
A.
viewpointFrom
Indicates a relationship where something is observed, depicted, or described from the perspective or location of a particular entity or point.
-
B.
viewOver
chosen
Indicates that one entity has a visual perspective overlooking or facing another entity, typically providing a vantage point onto it.
-
C.
towerViews
Indicates that a tower provides a view of, or overlooks, a particular place or object.
-
D.
viewingIs
Indicates that one entity is engaged in the act or state of viewing, observing, or watching another entity.
-
E.
perspectiveOf
Indicates that something is expressed, depicted, or understood from the viewpoint or standpoint of a particular entity.
- 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_69ca8314cd6c8190a6b8c2a1096e18f3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0ec200c8190b0299e2b0b4bdcc2 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:07 p.m.