Triple
T28050201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Singapore Exchange |
E708798
|
entity |
| Predicate | mainBoardListed |
P1278
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Singapore Exchange, mainBoardListed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainBoardListed Context triple: [Singapore Exchange, mainBoardListed, true]
-
A.
mainBoardFor
Indicates that one entity serves as the primary circuit board or central board used by another entity.
-
B.
mainBoardName
Indicates the name or designation assigned to a main board (e.g., primary circuit board or central hardware board) associated with an entity.
-
C.
listedOn
chosen
Indicates that an item, entity, or piece of information appears as an entry on a particular list, platform, or catalog.
-
D.
listedWith
Indicates that an entity is included as an item or entry within a particular list, catalog, or collection.
-
E.
hasListingBoard
Indicates that an entity is associated with or features a listing board used to display available items, offers, or information.
- 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_69f63fd88d408190af30ebec8469b050 |
completed | May 2, 2026, 6:18 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:32 p.m.