Triple
T224965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASDAQ |
E4293
|
entity |
| Predicate | primaryListingVenueFor |
P5921
|
FINISHED |
| Object | many U.S. technology companies |
—
|
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: many U.S. technology companies | Statement: [NASDAQ, primaryListingVenueFor, many U.S. technology companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryListingVenueFor Context triple: [NASDAQ, primaryListingVenueFor, many U.S. technology companies]
-
A.
primaryVenueFor
chosen
Indicates that one entity serves as the main or principal venue or location for events, activities, or operations associated with another entity.
-
B.
primaryVenues
Indicates the main or most important venues associated with or used by a given entity.
-
C.
venue
Indicates the place or location where an event, activity, or interaction takes place.
-
D.
servesVenue
Indicates that an entity provides services or functions in support of a particular venue.
-
E.
primaryTheater
Indicates that a particular location or region is the main setting or principal area where an event, activity, or operation takes place.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dec53ac8190912f3d79576131fa |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b5739dc8190bad8bfa330ce0499 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.