Triple
T18440076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cboe EDGX Exchange |
E450502
|
entity |
| Predicate | servesParticipantType |
P33564
|
FINISHED |
| Object | broker-dealers |
—
|
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: broker-dealers | Statement: [Cboe EDGX Exchange, servesParticipantType, broker-dealers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesParticipantType Context triple: [Cboe EDGX Exchange, servesParticipantType, broker-dealers]
-
A.
supportsParticipantType
chosen
Indicates that an entity is compatible with, or designed to work with, a specified type or category of participant.
-
B.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
C.
originalParticipantsType
Indicates the type or category of participants that were initially involved in an event, action, or relationship.
-
D.
servesMember
Indicates that one entity provides services or assistance to another entity that is considered its member.
-
E.
servesEventType
Indicates that an entity provides or supports a particular type or category of event.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c0fda908190901a108fb9982a2d |
completed | April 19, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e469c943a4819094c8fdc5971ad3a7 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:30 a.m.