Triple
T8826122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ERJ |
E210018
|
entity |
| Predicate | hasTradingStatus |
P5724
|
FINISHED |
| Object | actively traded |
—
|
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: actively traded | Statement: [ERJ, hasTradingStatus, actively traded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTradingStatus Context triple: [ERJ, hasTradingStatus, actively traded]
-
A.
tradingStatus
chosen
Indicates the current state or condition of an entity’s ability to be traded or engaged in trading activities.
-
B.
hasTradingSession
Indicates that an entity participates in or is associated with a specific trading session or period during which trading activities occur.
-
C.
hasMarketStatus
Indicates the current commercial or trading condition of an entity, such as whether it is active, suspended, listed, or delisted in a market.
-
D.
hasTradingHours
Indicates that an entity operates or is available for trading during specified time periods.
-
E.
hasTradingDays
Indicates that an entity is associated with specific days on which trading or commercial transactions are conducted.
- 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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc60332d208190972a8b03fbd760ee |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:46 p.m.