Triple
T27152546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amanohashidate |
E682428
|
entity |
| Predicate | appearsAsWhenUpsideDown |
P172789
|
FINISHED |
| Object | bridge to heaven |
—
|
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: bridge to heaven | Statement: [Amanohashidate, appearsAsWhenUpsideDown, bridge to heaven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsAsWhenUpsideDown Context triple: [Amanohashidate, appearsAsWhenUpsideDown, bridge to heaven]
-
A.
obverseOrReverse
Indicates that two sides or aspects of the same object or item are being related as its obverse (front) and reverse (back).
-
B.
depictedOnCoinReverse
Indicates that an entity is shown or represented on the reverse (back) side of a coin.
-
C.
obverseDepiction
Indicates that one entity is depicted on the obverse (front) side of another, such as the front face of a coin or medal.
-
D.
mirroredOn
Indicates that one entity is a reflective counterpart of another, such that its structure, appearance, or configuration is reversed or symmetrically aligned relative to the other.
-
E.
reversed
Indicates that the direction or order of a previously defined relationship or sequence between entities is inverted.
- 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_69eefaceb2a08190b9659b7f730629f5 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 27, 2026, 9:15 a.m.