Triple
T33651951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southbound Trading |
E862121
|
entity |
| Predicate | underlyingProgram |
P17523
|
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: [Southbound Trading, underlyingProgram, Bond Connect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingProgram Context triple: [Southbound Trading, underlyingProgram, Bond Connect]
-
A.
intendedProgram
Indicates the academic or training program that an entity plans or expects to pursue, rather than one they are currently enrolled in or have completed.
-
B.
originProgram
chosen
Indicates the program, initiative, or source project from which an entity, item, or record originally comes.
-
C.
mergedUnderProgram
Indicates that one entity has been combined or consolidated with another as part of a specific program or organized initiative.
-
D.
servedProgram
Indicates that an entity has provided, delivered, or made available a particular program to another party or context.
-
E.
initiatedUnderProgram
Indicates that an action or process was started as part of, or in accordance with, a specific program or initiative.
- 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_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 1, 2026, 1:42 a.m.