Triple
T12153167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johor Bahru District |
E289507
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Senai |
E840636
|
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: Senai | Statement: [Johor Bahru District, contains, Senai]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Senai Context triple: [Johor Bahru District, contains, Senai]
-
A.
Senai
chosen
Senai is a town in Johor, Malaysia, best known for housing Senai International Airport and serving as a key industrial and logistics hub near Skudai.
-
B.
Sene
Sene is the tenth month of the Ethiopian calendar, roughly corresponding to June in the Gregorian calendar.
-
C.
Seini
Seini is a small town in northwestern Romania, known for its industrial activities and location near the Lăpuș River in Maramureș County.
-
D.
Es Sénia
Es Sénia is a commune and suburb of Oran in northwestern Algeria, known for hosting the region’s main international airport and various industrial and educational facilities.
-
E.
Senesky
Senesky is a surname most notably associated with George Senesky, an American professional basketball player and coach in the mid-20th century.
- 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915bf615c8190ad5f8ae8665678dc |
completed | April 10, 2026, 3:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f69aa2e88190aaa58468571d6dad |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 8, 2026, 9:49 p.m.