Triple
T33745369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Penh |
E864683
|
entity |
| Predicate | hasLegendEvent |
P1582
|
FINISHED |
| Object | discovery of Buddha statues in a tree trunk |
—
|
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: discovery of Buddha statues in a tree trunk | Statement: [Lady Penh, hasLegendEvent, discovery of Buddha statues in a tree trunk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegendEvent Context triple: [Lady Penh, hasLegendEvent, discovery of Buddha statues in a tree trunk]
-
A.
hasLegendAssociatedWith
chosen
Indicates that something is connected to or accompanied by a traditional story, myth, or legend.
-
B.
hasHistoricalLegend
Indicates that there exists a traditional story, myth, or legend associated with the subject, typically rooted in historical or cultural narratives.
-
C.
hasSiblingInLegend
Indicates that one entity is described as the sibling of another entity within a mythological or legendary narrative.
-
D.
hasSiteRelatedToLegend
Indicates that a site is associated with, or thematically connected to, a particular legend or legendary narrative.
-
E.
mentionsLegend
Indicates that one entity makes reference to or cites a legendary figure, story, or concept associated with 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_69f3498b24b8819096a65009e521d0e1 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: May 1, 2026, 1:44 a.m.