Triple
T27745690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Armco Steel |
E701975
|
entity |
| Predicate | stockExchangeListedOn |
P46907
|
FINISHED |
| Object | New York Stock Exchange |
—
|
NE NERFINISHED |
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: New York Stock Exchange | Statement: [Armco Steel, stockExchangeListedOn, New York Stock Exchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stockExchangeListedOn Context triple: [Armco Steel, stockExchangeListedOn, New York Stock Exchange]
-
A.
governsStockExchangeListedOn
Indicates that one entity has regulatory or administrative authority over the stock exchange on which another entity is listed.
-
B.
sharesListedOn
chosen
Indicates that a company's shares are officially listed and traded on a specified stock exchange.
-
C.
tradedOn
Indicates that an asset, security, or instrument is bought and sold on a particular exchange or trading venue.
-
D.
canBeListedOnStockExchange
Indicates that an entity meets the necessary conditions to be eligible for listing and trading on a stock exchange.
-
E.
hasStockExchange
Indicates that an entity is associated with or listed on a particular stock exchange.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63719b84c81909c805036f6717239 |
completed | May 2, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:15 p.m.