Triple
T33651836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | China interbank bond market |
E862118
|
entity |
| Predicate | foreignAccessMechanism |
P5872
|
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, foreignAccessMechanism, Bond Connect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foreignAccessMechanism Context triple: [China interbank bond market, foreignAccessMechanism, Bond Connect]
-
A.
accessMethod
chosen
Indicates the means, process, or technique by which something is accessed, retrieved, or made available.
-
B.
secondaryAccessMode
Indicates an additional, non-primary way in which an entity can be accessed, used, or interacted with.
-
C.
accessProtocol
Indicates the method or rules by which one entity is allowed to access or communicate with another entity or resource.
-
D.
typeOfAccess
Indicates the specific kind or level of access that one entity has to another (such as read, write, or execute permissions).
-
E.
accessMode
Indicates the manner or method by which an entity can be accessed, used, or interacted with.
- 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_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:42 a.m.