Triple
T15853112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BIT |
E384388
|
entity |
| Predicate | notationIn |
P89229
|
FINISHED |
| Object | international financial markets |
—
|
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: international financial markets | Statement: [BIT, notationIn, international financial markets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notationIn Context triple: [BIT, notationIn, international financial markets]
-
A.
notation
Indicates a conventional way of symbolically representing or writing something, such as concepts, quantities, or operations, within a specific system.
-
B.
notationType
Indicates the specific system or style of notation used to represent or encode something (such as music, math, or language).
-
C.
notationLanguage
Indicates the language or symbolic system in which a notation or formal representation is expressed.
-
D.
informalNotation
Indicates that an entity is represented or expressed using a non-standard, simplified, or colloquial form of notation rather than a formal or fully rigorous one.
-
E.
notationPurpose
chosen
Indicates that one notation is used with the specific purpose or function of representing, explaining, or supporting another entity or concept.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142b976c081908d3ba3e705419f3a |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:50 a.m.