Triple
T37802356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fukuoka Stock Exchange |
E942411
|
entity |
| Predicate | servesParticipant |
P91223
|
FINISHED |
| Object | brokerage firms |
—
|
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: brokerage firms | Statement: [Fukuoka Stock Exchange, servesParticipant, brokerage firms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesParticipant Context triple: [Fukuoka Stock Exchange, servesParticipant, brokerage firms]
-
A.
providesToParticipants
chosen
Indicates that something is supplied, given, or made available to the participants in an event, activity, or context.
-
B.
servesEvent
Indicates that an entity provides, hosts, or facilitates a particular event for others.
-
C.
servesMember
Indicates that one entity provides services or assistance to another entity that is considered its member.
-
D.
participantWith
Indicates that an entity takes part in an event, activity, or process together with another specified entity.
-
E.
participantFrom
Indicates that a participant originates from, is associated with, or comes out of a specified source, group, or context.
- 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_69f76ee6f1f4819091e2cf9c9e6aee19 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a008098e5dc8190b7ccad8bab780343 |
completed | May 10, 2026, 12:56 p.m. |
| PD | Predicate disambiguation | batch_6a008037267c8190990225a6ff0b3694 |
completed | May 10, 2026, 12:55 p.m. |
Created at: May 3, 2026, 4:19 p.m.