Triple
T11741698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Togetsukyo Bridge |
E279170
|
entity |
| Predicate | notableViewpointFor |
P9787
|
FINISHED |
| Object | cherry blossom viewing |
—
|
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: cherry blossom viewing | Statement: [Togetsukyo Bridge, notableViewpointFor, cherry blossom viewing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableViewpointFor Context triple: [Togetsukyo Bridge, notableViewpointFor, cherry blossom viewing]
-
A.
notableViewpoints
Indicates that an entity is associated with significant or noteworthy viewpoints, perspectives, or opinions.
-
B.
notAbout
Indicates that a given entity, statement, or resource does not concern, reference, or pertain to another specified entity or topic.
-
C.
viewpointFrom
chosen
Indicates a relationship where something is observed, depicted, or described from the perspective or location of a particular entity or point.
-
D.
nonVoting
Indicates that an entity participates in a group or organization without possessing the right to vote in its decisions.
-
E.
notableOpinion
Indicates that one entity holds a significant or widely recognized opinion or viewpoint about another 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4f191388190bd6ef7e80c41ca48 |
completed | April 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69d88a813cc48190a3dfdc60e8af80ae |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.