Triple
T32576188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gongsun Hong |
E832649
|
entity |
| Predicate | implementedPolicyType |
P94620
|
FINISHED |
| Object | centralizing policies |
—
|
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: centralizing policies | Statement: [Gongsun Hong, implementedPolicyType, centralizing policies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementedPolicyType Context triple: [Gongsun Hong, implementedPolicyType, centralizing policies]
-
A.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
-
B.
appliesPolicyType
Indicates that a specific policy type is applied to or enforced on a given entity or context.
-
C.
implementsPolicyFrom
Indicates that one entity carries out, enforces, or operationalizes a policy that originates from another entity.
-
D.
establishedPolicy
Indicates that a policy has been formally created, adopted, and put into effect as a guiding rule or standard.
-
E.
implementationType
chosen
Indicates the specific manner or approach by which something is implemented or realized in practice.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:04 a.m.