Triple
T8442879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tam Phủ |
E199590
|
entity |
| Predicate | sharesTraditionWith |
P11721
|
FINISHED |
| Object | Tứ Phủ |
E199590
|
NE 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: Tứ Phủ | Statement: [Tam Phủ, sharesTraditionWith, Tứ Phủ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tứ Phủ Context triple: [Tam Phủ, sharesTraditionWith, Tứ Phủ]
-
A.
Tam Phủ
chosen
Tam Phủ is a major cult within Vietnamese folk religion that venerates a trinity of Mother Goddesses associated with the heavens, waters, and forests, forming a core part of the Đạo Mẫu (Mother Goddess) tradition.
-
B.
Yen Phu
Yen Phu is a historic residential neighborhood in Hanoi, Vietnam, known for its traditional village atmosphere and scenic location along West Lake.
-
C.
Thiên Phúc
Thiên Phúc was the era name proclaimed by Emperor Lê Hoàn of Đại Cồ Việt, marking a specific reign period in early Vietnamese history.
-
D.
Ngã Tư Sở
Ngã Tư Sở is a major traffic junction and commercial hub in southwestern Hanoi, Vietnam, connecting several key urban districts.
-
E.
Phúc Lợi
Phúc Lợi is a ward-level administrative subdivision located within Long Biên District of Hanoi, Vietnam.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca83170f9081909cd98f55614c6476 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe310d8e08190b871bda79acde678 |
completed | March 31, 2026, 3:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce1da3a99481909c9beae665bb5b83 |
completed | April 2, 2026, 7:41 a.m. |
Created at: March 30, 2026, 6:08 p.m.