Triple
T23319166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaspar de Portolá |
E590798
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Portolá |
—
|
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: Portolá | Statement: [Gaspar de Portolá, familyName, Portolá]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Portolá Context triple: [Gaspar de Portolá, familyName, Portolá]
-
A.
Portolá
chosen
Portolá is a Spanish surname most notably associated with Gaspar de Portolá, the 18th-century explorer and first Spanish governor of Alta California.
-
B.
Villalobón
Villalobón is a small municipality in the autonomous community of Castile and León in northern Spain.
-
C.
Portola
Portola is a residential neighborhood in southeastern San Francisco known for its hillside streets, diverse community, and proximity to Visitacion Valley.
-
D.
Colón
Colón is a town in El Salvador’s La Libertad Department, known as a local municipal center within the region.
-
E.
Colón
Colón is a municipality and city in western Cuba known for its agricultural surroundings and colonial-era architecture.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1978372948190bad066893c4e0768 |
completed | April 29, 2026, 5:30 a.m. |
Created at: April 17, 2026, 5:07 p.m.