Triple

T21517206
Position Surface form Disambiguated ID Type / Status
Subject Maynas Province E530875 entity
Predicate namedAfter P63 FINISHED
Object Maynas NE NERFINISHED

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: Maynas | Statement: [Maynas Province, namedAfter, Maynas]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maynas
Context triple: [Maynas Province, namedAfter, Maynas]
  • A. Maynas chosen
    Maynas was a historical region and indigenous group in the Amazon Basin, whose name was later used for the Maynas Province in Peru.
  • B. Manticao
    Manticao is a coastal municipality in the province of Misamis Oriental on the island of Mindanao in the Philippines.
  • C. Mazatenango
    Mazatenango is a major commercial and transportation hub in southwestern Guatemala, known for its vibrant markets and regional agricultural trade.
  • D. Atalaya
    Atalaya is a small Peruvian river port town in the Amazon rainforest, serving as a regional hub for transport and trade.
  • E. Cainteña
    Cainteña is the Spanish-derived demonym referring to a female resident or native of Cainta, a municipality in the province of Rizal in the Philippines.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c45d95a081908e7962ad215da746 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ee814278e08190a66d516bed0726b5 completed April 26, 2026, 9:18 p.m.
Created at: April 16, 2026, 6:25 p.m.