Triple
T7208335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selaru language |
E148731
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Selaro |
E648907
|
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: Selaro | Statement: [Selaru language, hasAlternativeName, Selaro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Selaro Context triple: [Selaru language, hasAlternativeName, Selaro]
-
A.
Selaaru
Selaaru is an Austronesian language spoken on Selaru Island in Indonesia’s Tanimbar Islands.
-
B.
Selaru
chosen
Selaru is an Austronesian language spoken by the Selaru people on Selaru Island in Indonesia’s Tanimbar archipelago.
-
C.
Sardoal
Sardoal is a small Portuguese municipality known for its historic village center and traditional religious and cultural festivities, located in the Centro Region of Portugal.
-
D.
Lumarzo
Lumarzo is a small municipality in the Liguria region of northwestern Italy, located in the hilly inland area near Genoa.
-
E.
Lodoselo
Lodoselo is a small village in the municipality of Sarreaus, in the province of Ourense, Galicia, Spain.
- 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_69c687e8cf188190b5f3ecffd681f04e |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e96ae4dc8190b0b9e064ff968c10 |
completed | March 27, 2026, 8:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7d381a7288190bbfdb8f1de6b5f05 |
completed | March 28, 2026, 1:11 p.m. |
Created at: March 27, 2026, 2:52 p.m.