Triple
T28050300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Section of Tokyo Stock Exchange |
E708800
|
entity |
| Predicate | hasListingBoardType |
P71981
|
FINISHED |
| Object | equity securities |
—
|
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: equity securities | Statement: [First Section of Tokyo Stock Exchange, hasListingBoardType, equity securities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasListingBoardType Context triple: [First Section of Tokyo Stock Exchange, hasListingBoardType, equity securities]
-
A.
hasListingBoard
Indicates that an entity is associated with or features a listing board used to display available items, offers, or information.
-
B.
hasBoardType
chosen
Indicates that an entity is associated with or uses a specific type or category of board.
-
C.
hasListingVenue
Indicates that an item, event, or offering is associated with the specific venue where it is listed or made available.
-
D.
hasListingSystem
Indicates that an entity is associated with or uses a particular system or mechanism for listing or cataloging items, entries, or information.
-
E.
hasBenchType
Indicates that an entity is associated with or characterized by a specific type or category of bench.
- 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_69ef9b6df9f48190bbb971d02cbe1b65 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 27, 2026, 8:32 p.m.