Triple
T7154785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Société Anonyme |
E166781
|
entity |
| Predicate | possibleListingVenue |
P41818
|
FINISHED |
| Object | regulated markets |
—
|
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: regulated markets | Statement: [Société Anonyme, possibleListingVenue, regulated markets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleListingVenue Context triple: [Société Anonyme, possibleListingVenue, regulated markets]
-
A.
hasListingVenue
chosen
Indicates that an item, event, or offering is associated with the specific venue where it is listed or made available.
-
B.
isRegularVenueFor
Indicates that a location is commonly or routinely used as the venue for a particular event, activity, or entity’s gatherings.
-
C.
homeVenueOwned
Indicates that the specified home venue is legally owned or possessed by the associated entity.
-
D.
homeVenueAlsoUsedBy
Indicates that the venue serving as a home location for one entity is also used as a venue by another entity.
-
E.
homeVenueCountry
Indicates the country in which an entity’s primary or home venue is located.
- 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_69c68887a5cc8190bec0ea96227164f7 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e80c747c8190a017a2b1c3e78a3f |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1caf4e48190b47bb398a3c1554d |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:46 p.m.