Triple
T31943214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asakusa Kannon legend |
E815580
|
entity |
| Predicate | describesDiscoveryOf |
P27994
|
FINISHED |
| Object | Kannon statue |
—
|
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: Kannon statue | Statement: [Asakusa Kannon legend, describesDiscoveryOf, Kannon statue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesDiscoveryOf Context triple: [Asakusa Kannon legend, describesDiscoveryOf, Kannon statue]
-
A.
madeDiscoveryOn
Indicates that an entity discovered or identified something on a specific date or at a specific point in time.
-
B.
reportsDiscoveryOf
chosen
Indicates that one entity formally announces or documents the finding or uncovering of another entity (typically a new object, fact, or phenomenon).
-
C.
discovery
Indicates the event or process by which one entity finds, uncovers, or identifies something previously unknown or unrecognized.
-
D.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
E.
namedForDiscoveryOf
Indicates that one entity is named in recognition of another entity’s discovery of something.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 12:06 a.m.