Triple
T7235243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanunoo language |
E155204
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Hanunóo |
E174383
|
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: Hanunóo | Statement: [Hanunoo language, hasAlternativeName, Hanunóo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hanunóo Context triple: [Hanunoo language, hasAlternativeName, Hanunóo]
-
A.
Hanunoo
chosen
Hanunoo is an indigenous Philippine script traditionally used by the Hanunó'o Mangyan people of Mindoro to write their Austronesian language.
-
B.
Maganlal
Maganlal is an Indian given name commonly used for men, particularly in Gujarati-speaking communities.
-
C.
Agutaynen
Agutaynen is an Austronesian language spoken by the Agutaynen people in the Philippines, primarily in the province of Palawan.
-
D.
Anilio
Anilio is a mountain village in the Metsovo region of Epirus in northwestern Greece, known for its traditional architecture and alpine setting.
-
E.
Dupax Isinay
Dupax Isinay is a regional dialect of the Isinay language traditionally spoken in the Dupax area 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_69c688143bfc81908d4176617735e601 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea130e5c819087f74883760fe327 |
completed | March 27, 2026, 8:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7d38b5ac4819083837b149ec9e3ea |
completed | March 28, 2026, 1:11 p.m. |
Created at: March 27, 2026, 2:55 p.m.