Triple
T35382565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lung Yeuk Tau |
E1022689
|
entity |
| Predicate | hasAncestralHall |
P147258
|
FINISHED |
| Object | Tang Chung Ling Ancestral Hall |
—
|
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: Tang Chung Ling Ancestral Hall | Statement: [Lung Yeuk Tau, hasAncestralHall, Tang Chung Ling Ancestral Hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncestralHall Context triple: [Lung Yeuk Tau, hasAncestralHall, Tang Chung Ling Ancestral Hall]
-
A.
hasAncestralPalace
Indicates that an entity possesses or is associated with a palace inherited from its ancestors or historically belonging to its lineage.
-
B.
hasAncestralResidence
chosen
Indicates that an entity has a residence or dwelling place that belonged to or was established by its ancestors.
-
C.
hasAncestralHarbour
Indicates that an entity has a harbour that historically served as the origin or ancestral port associated with it.
-
D.
hasAncestralLand
Indicates that an entity possesses land inherited from its ancestors or traditionally associated with its lineage.
-
E.
hasMainHall
Indicates that an entity possesses or includes a primary or central hall as a significant internal space.
- 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 3, 2026, 4:03 p.m.