Triple
T17255492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SalamAir |
E418869
|
entity |
| Predicate | cityServed |
P82
|
FINISHED |
| Object | Sohar |
E580314
|
NE 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: Sohar | Statement: [SalamAir, cityServed, Sohar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sohar Context triple: [SalamAir, cityServed, Sohar]
-
A.
Sohar
chosen
Sohar is a coastal city in northern Oman known as an important industrial and port hub on the Gulf of Oman.
-
B.
Sohar
Sohar is a traditional Bhojpuri folk song genre typically performed by women to celebrate childbirth and related rituals.
-
C.
Port of Sohar
The Port of Sohar is a major deep-sea industrial and commercial port in northern Oman that serves as a key regional hub for shipping, logistics, and heavy industries.
-
D.
Salalah
Salalah is a coastal city in southern Oman known for its monsoon-cooled climate, lush green landscapes, and role as a regional tourism and commercial hub.
-
E.
Warud
Warud is a town in Maharashtra, India, known for its orange production and location within the Amravati district.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e6c362c819088965c6e05f33faf |
completed | April 19, 2026, 1:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a017942ae108190ac6ec61514ba58b4 |
completed | May 11, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:39 a.m.