Triple
T9233227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SBRY |
E221872
|
entity |
| Predicate | hasTradingSegment |
P64613
|
FINISHED |
| Object | Premium Listing |
—
|
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: Premium Listing | Statement: [SBRY, hasTradingSegment, Premium Listing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTradingSegment Context triple: [SBRY, hasTradingSegment, Premium Listing]
-
A.
tradingSegment
chosen
Indicates that one entity operates within, or is associated with, a specific trading segment or market subdivision for transactional 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.
hasTradingVenueType
Indicates the specific category or type of trading venue associated with a given trading platform or marketplace.
-
D.
hasTradingVenueCode
Indicates that an entity is associated with a specific trading venue through its designated code.
-
E.
hasTradingHours
Indicates that an entity operates or is available for trading during specified time periods.
- 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccee1baa3c8190870d1e850ccab1e0 |
completed | April 1, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
Created at: March 30, 2026, 7:29 p.m.