Triple
T31591651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBY |
E806112
|
entity |
| Predicate | isListedSecurity |
P171996
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [BBY, isListedSecurity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isListedSecurity Context triple: [BBY, isListedSecurity, true]
-
A.
isListedSecurityOf
Indicates that one entity is a security (such as a stock or bond) that is officially listed and traded on the other entity, which is a financial exchange or trading venue.
-
B.
isListed
Indicates that an entity appears on or is included in a specified list, registry, or catalog.
-
C.
isListedBy
Indicates that one entity appears as an item or entry in a list, catalog, or register maintained or provided by another entity.
-
D.
canBeListedOnStockExchange
Indicates that an entity meets the necessary conditions to be eligible for listing and trading on a stock exchange.
-
E.
isListedEntityThrough
Indicates that one entity is recognized or recorded as a listed entity by means of, or via the involvement of, another entity or mechanism.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:28 p.m.