Triple
T1937480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VZ |
E41474
|
entity |
| Predicate | tradedInMarket |
P6939
|
FINISHED |
| Object | US Equity Market |
—
|
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: US Equity Market | Statement: [VZ, tradedInMarket, US Equity Market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradedInMarket Context triple: [VZ, tradedInMarket, US Equity Market]
-
A.
tradedIn
Indicates that one entity has given up or exchanged another entity, typically as part of a transaction to obtain something else.
-
B.
tradedTo
Indicates that ownership or contractual rights to an entity (such as a player, asset, or item) were transferred from one party to another, typically as part of an exchange or deal.
-
C.
tradedSince
Indicates that an entity has been actively traded starting from a specified point in time and continuing thereafter.
-
D.
tradedOn
chosen
Indicates that an asset, security, or instrument is bought and sold on a particular exchange or trading venue.
-
E.
hasTrade
Indicates a relationship where one entity engages in or maintains a commercial exchange or trading activity with another entity.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb2c752fc81909baf38ff1cdeb18c |
completed | March 7, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69abaff07cf88190b4883c5f17f90abd |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.