Triple
T28837918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nam Thiên Đệ Nhất Động |
E728234
|
entity |
| Predicate | associatedSiteUse |
P62923
|
FINISHED |
| Object | Buddhist pilgrimage site |
—
|
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: Buddhist pilgrimage site | Statement: [Nam Thiên Đệ Nhất Động, associatedSiteUse, Buddhist pilgrimage site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSiteUse Context triple: [Nam Thiên Đệ Nhất Động, associatedSiteUse, Buddhist pilgrimage site]
-
A.
associatedSiteType
Indicates the type or category of site with which an entity is associated.
-
B.
hasSiteUse
chosen
Indicates that a site is used or designated for a particular function, activity, or purpose.
-
C.
currentSiteUse
Indicates how a site is presently being used or the function it currently serves.
-
D.
associatedWithVenueSecondaryUse
Indicates that an entity has a secondary or supplementary association with a particular venue, beyond its primary or main use.
-
E.
originalSiteUse
Indicates the historical or initial functional use or purpose assigned to a particular site before any subsequent changes or developments.
- 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_69f0319e8e7c8190b37288c8845b9dbc |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a01ed1790148190b08c1dba53de4371 |
completed | May 11, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_6a01e9c20798819085760b377dc7b3fa |
completed | May 11, 2026, 2:37 p.m. |
Created at: April 28, 2026, 6:39 a.m.