Triple
T30968947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North–South Railway (Saudi Arabia) |
E789036
|
entity |
| Predicate | servesMine |
P173547
|
FINISHED |
| Object | phosphate mines in northern Saudi Arabia |
—
|
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: phosphate mines in northern Saudi Arabia | Statement: [North–South Railway (Saudi Arabia), servesMine, phosphate mines in northern Saudi Arabia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesMine Context triple: [North–South Railway (Saudi Arabia), servesMine, phosphate mines in northern Saudi Arabia]
-
A.
isServed
Indicates that one entity provides or delivers a service, product, or assistance to another entity.
-
B.
mayServe
Indicates that one entity is permitted or authorized to provide a service or function to another entity.
-
C.
isServedFor
Indicates that something is provided or presented as suitable or intended for a particular purpose, use, or recipient.
-
D.
someServe
chosen
Indicates that one entity serves, assists, or performs duties for another entity in some capacity.
-
E.
mayServeAt
Indicates that one entity is permitted or authorized to perform service or duties at a specified location, organization, or context.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: April 29, 2026, 8:54 p.m.