Triple
T30989582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samba Capital |
E789627
|
entity |
| Predicate | listingVenueFocus |
P170888
|
FINISHED |
| Object | Tadawul |
—
|
NE NERFINISHED |
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: Tadawul | Statement: [Samba Capital, listingVenueFocus, Tadawul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listingVenueFocus Context triple: [Samba Capital, listingVenueFocus, Tadawul]
-
A.
homeVenueFocus
Indicates a primary or central emphasis on a particular venue as the main location associated with an entity’s activities or presence.
-
B.
featuresVenue
Indicates that one entity includes, hosts, or is associated with a particular venue as part of its offering or context.
-
C.
amenityFocus
Indicates a relationship where an amenity is specifically oriented toward, designed for, or primarily serving a particular focus or target (such as a user group, activity, or purpose).
-
D.
primaryVenues
Indicates the main or most important venues associated with or used by a given entity.
-
E.
primaryVenueFor
Indicates that one entity serves as the main or principal venue or location for events, activities, or operations associated with another entity.
- F. None of above. chosen
Provenance (4 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 29, 2026, 8:56 p.m.