Triple
T30539131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qiddiya Investment Company |
E777226
|
entity |
| Predicate | locatedProjectNear |
P69562
|
FINISHED |
| Object | Riyadh |
—
|
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: Riyadh | Statement: [Qiddiya Investment Company, locatedProjectNear, Riyadh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedProjectNear Context triple: [Qiddiya Investment Company, locatedProjectNear, Riyadh]
-
A.
nearbyProject
Indicates that one entity is located close to or in the immediate vicinity of another entity or project.
-
B.
locatedNearPass
Indicates that one entity is situated close to a mountain pass or similar passageway.
-
C.
hasNearbyProject
chosen
Indicates that one entity has a project located within a close or specified proximity to another entity or reference point.
-
D.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
E.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
- 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_69f2249d183c8190b79937c1768d2163 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a00c3362dcc819096e49b882709fddd |
completed | May 10, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_6a00c2e5cdd88190a5f2d0f6a843cd56 |
completed | May 10, 2026, 5:39 p.m. |
Created at: April 29, 2026, 8:19 p.m.