Triple
T33745384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Penh |
E864683
|
entity |
| Predicate | hasCanonicalSite |
P19451
|
FINISHED |
| Object | Wat Phnom historical site |
—
|
NE NERFINISHED |
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: Wat Phnom historical site | Statement: [Lady Penh, hasCanonicalSite, Wat Phnom historical site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalSite Context triple: [Lady Penh, hasCanonicalSite, Wat Phnom historical site]
-
A.
hasCanonicalUrl
Indicates that an entity is associated with its primary, authoritative URL that should be used as its standard web address.
-
B.
hasMainSite
chosen
Indicates that one entity is designated as the primary or central site associated with another entity.
-
C.
hasCanonicalReference
Indicates that one entity serves as the authoritative or standard reference source for another entity.
-
D.
isCanonical
Indicates that something represents the standard, authoritative, or officially accepted form within a given context or system.
-
E.
hasCanonicalCategory
Indicates that something is associated with its standard or officially recognized category within a classification system.
- 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_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: May 1, 2026, 1:44 a.m.