Triple
T723710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XNYS |
E14673
|
entity |
| Predicate | isPrimaryListingVenueFor |
P5921
|
FINISHED |
| Object | many large-cap U.S. 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 large-cap U.S. companies | Statement: [XNYS, isPrimaryListingVenueFor, many large-cap U.S. companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrimaryListingVenueFor Context triple: [XNYS, isPrimaryListingVenueFor, many large-cap U.S. 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.
homeVenueOwned
Indicates that the specified home venue is legally owned or possessed by the associated entity.
-
C.
primaryListing
Indicates that one item in a set of listings is designated as the main or most authoritative listing for a given entity or context.
-
D.
primaryVenues
Indicates the main or most important venues associated with or used by a given entity.
-
E.
servesVenue
Indicates that an entity provides services or functions in support of a particular venue.
- 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a5a5360c8190b16e1e4f4206d0aa |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f700cc81908c6de3eedf68433c |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.