Triple
T29532661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People's Committee of Hợp Thanh Commune |
E749247
|
entity |
| Predicate | appliesStatePolicies |
P141280
|
FINISHED |
| Object | Hợp Thanh Commune |
—
|
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: Hợp Thanh Commune | Statement: [People's Committee of Hợp Thanh Commune, appliesStatePolicies, Hợp Thanh Commune]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesStatePolicies Context triple: [People's Committee of Hợp Thanh Commune, appliesStatePolicies, Hợp Thanh Commune]
-
A.
appliesPoliciesOf
chosen
Indicates that one entity enforces, follows, or implements the policies that originate from or are defined by another entity.
-
B.
appliesPolicyOn
Indicates that one entity enforces, executes, or brings into effect a specific policy on another entity or context.
-
C.
appliesPolicyType
Indicates that a specific policy type is applied to or enforced on a given entity or context.
-
D.
appliesToPolicy
Indicates that something is relevant or applicable to a particular policy.
-
E.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
- 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_69f0bd47abb081909bd6e6a33d770fd8 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fd64bc86848190a49f451a8fc5cf1e |
completed | May 8, 2026, 4:21 a.m. |
| PD | Predicate disambiguation | batch_69fd5ff4a648819090756d90fd195d9a |
completed | May 8, 2026, 4 a.m. |
Created at: April 28, 2026, 4:54 p.m.