Triple
T8020854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Section |
E186736
|
entity |
| Predicate | exchangeType |
P80605
|
FINISHED |
| Object | securities exchange segment |
—
|
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: securities exchange segment | Statement: [Second Section, exchangeType, securities exchange segment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exchangeType Context triple: [Second Section, exchangeType, securities exchange segment]
-
A.
exchangeRegime
Indicates the type of currency exchange system or policy framework governing how a country’s currency is valued and traded relative to other currencies.
-
B.
exchangeAuthority
Indicates a relationship where control or decision-making power is transferred or swapped between entities.
-
C.
exchangeSymbolType
Indicates the type or category of symbol used to represent an asset on a particular exchange.
-
D.
exchangeSymbol
Indicates that one entity serves as the ticker or trading symbol used to represent another entity on a specific exchange.
-
E.
exchangeFormat
Indicates that one entity uses, supports, or is represented in a particular data or communication format for exchanging information with another system or entity.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e8d90488190b57d1e748e272061 |
completed | March 31, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:20 p.m.