Triple
T6973884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSE Limited |
E161665
|
entity |
| Predicate | hasMainEquityBoard |
P73597
|
FINISHED |
| Object | Main Board |
—
|
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: Main Board | Statement: [JSE Limited, hasMainEquityBoard, Main Board]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainEquityBoard Context triple: [JSE Limited, hasMainEquityBoard, Main Board]
-
A.
hasBoardComposition
Indicates that an entity has a specific structure or makeup of its governing board, such as the types or proportions of members who serve on it.
-
B.
hasBoardType
Indicates that an entity is associated with or uses a specific type or category of board.
-
C.
hasBoardSize
Indicates that an entity is associated with a board whose dimensions or overall size are specified.
-
D.
mainBoardName
Indicates the name or designation assigned to a main board (e.g., primary circuit board or central hardware board) associated with an entity.
-
E.
hasLocalBoards
Indicates that an entity is associated with one or more governing or administrative boards operating at a local or regional level.
- F. None of above. chosen
Provenance (4 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_69c68854a0d88190bc0bf82263f1afce |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db3aad108190b19df2d21f5ce168 |
completed | March 27, 2026, 7:32 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c262508190a7708b3d9cf23d7c |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8e2d7b48190b37bb13984663cde |
completed | March 27, 2026, 7:22 p.m. |
Created at: March 27, 2026, 2:30 p.m.