Triple
T15758893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rim-Sin I |
E382040
|
entity |
| Predicate | mainOpponent |
P437
|
FINISHED |
| Object | Isin |
E766869
|
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: Isin | Statement: [Rim-Sin I, mainOpponent, Isin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Isin Context triple: [Rim-Sin I, mainOpponent, Isin]
-
A.
Isin
Isin is a local government area in Kwara State, Nigeria, known for its predominantly Yoruba communities and agrarian economy.
-
B.
Isin
chosen
Isin was an important ancient Mesopotamian city-state in southern Iraq, notable for its political and religious significance during the early second millennium BCE.
-
C.
Isinay
Isinay is an Austronesian language spoken by the Isinay people of northern Luzon in the Philippines, noted for its distinct phonology and grammar compared to neighboring Philippine languages.
-
D.
Isanzu
Isanzu is a Bantu language spoken by the Isanzu people of north-central Tanzania.
-
E.
Isinai
Isinai is an Austronesian language spoken by the Isinai people of Nueva Vizcaya in the northern Philippines.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e050b35ea48190a758ee76a57b5451 |
completed | April 16, 2026, 3 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff8774eda08190a6231b4fd5027e6f |
completed | May 9, 2026, 7:13 p.m. |
Created at: April 10, 2026, 4:47 a.m.