Triple
T11651325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TRVG |
E276909
|
entity |
| Predicate | isElectronicTradingSymbol |
P100190
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [TRVG, isElectronicTradingSymbol, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isElectronicTradingSymbol Context triple: [TRVG, isElectronicTradingSymbol, yes]
-
A.
hasElectronicTradingSystem
Indicates that an entity operates or utilizes an electronic system for executing trades or transactions.
-
B.
electronicTradingPlatform
Indicates a relationship where financial instruments are bought and sold through an electronic trading system or marketplace rather than via traditional manual or floor-based methods.
-
C.
isExchangeTraded
Indicates that the entity is traded on a formal exchange or marketplace rather than over-the-counter or privately.
-
D.
isOptionsTraded
Indicates that options contracts based on the referenced entity are actively traded in a financial market.
-
E.
tradedOn
Indicates that an asset, security, or instrument is bought and sold on a particular exchange or trading venue.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2cea9308190a13f7dd995ea07a4 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
| PDg | Predicate description generation | batch_69d87f30642c8190ad94fa061cde186b |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:39 p.m.