Triple
T33651834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | China interbank bond market |
E862118
|
entity |
| Predicate | allowsProgram |
P273
|
FINISHED |
| Object | Bond Connect |
—
|
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: Bond Connect | Statement: [China interbank bond market, allowsProgram, Bond Connect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsProgram Context triple: [China interbank bond market, allowsProgram, Bond Connect]
-
A.
authorizesProgram
Indicates that one entity grants official permission for a particular program to exist, operate, or proceed.
-
B.
supportsProgramOf
Indicates that one entity provides assistance, resources, or endorsement to help another entity’s program operate or succeed.
-
C.
allows
chosen
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
D.
authorizedUnderProgram
Indicates that an entity’s action, status, or participation is permitted or governed according to the rules or provisions of a specific program.
-
E.
appliesProgram
Indicates that an agent initiates or carries out a specific program, procedure, or course of action on or for a target entity.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 1, 2026, 1:42 a.m.