Triple
T29006615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Phat Diem |
E736452
|
entity |
| Predicate | primarySeeCity |
P136244
|
FINISHED |
| Object | Phat Diem |
—
|
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: Phat Diem | Statement: [Diocese of Phat Diem, primarySeeCity, Phat Diem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySeeCity Context triple: [Diocese of Phat Diem, primarySeeCity, Phat Diem]
-
A.
secondarySeeCity
Indicates that an entity has a secondary or less prominent association with a particular city.
-
B.
primaryCity
Indicates that one city serves as the main or most important city associated with a given region, entity, or context.
-
C.
city2
Indicates a relationship where one entity is identified as a city associated with, located in, or otherwise linked to another entity.
-
D.
primaryLocationCity
chosen
Indicates the city that serves as the main or primary location associated with the subject.
-
E.
primaryCityDocumented
Indicates that a city is recorded or designated as the main or principal city associated with a given entity or context.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a00a2f0d1588190a936ea7df0ef0464 |
completed | May 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_6a00a28ccd94819085b5e123f5a4769e |
completed | May 10, 2026, 3:21 p.m. |
Created at: April 28, 2026, 9:38 a.m.