Triple
T25591121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gobernaciones marítimas de Chile |
E641523
|
entity |
| Predicate | tienenAlFrente |
P4990
|
FINISHED |
| Object | gobernador marítimo |
—
|
LITERAL 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: gobernador marítimo | Statement: [gobernaciones marítimas de Chile, tienenAlFrente, gobernador marítimo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tienenAlFrente Context triple: [gobernaciones marítimas de Chile, tienenAlFrente, gobernador marítimo]
-
A.
frontOf
Indicates that one entity is positioned directly before another along a primary viewing or movement direction.
-
B.
frontIn
Indicates that one entity is positioned directly in front of another entity in space or sequence.
-
C.
hasFront
chosen
Indicates that an entity possesses or is associated with a front-facing side, surface, or portion.
-
D.
commonlyFrontedBy
Indicates that one element is typically placed at the beginning or in the leading position of another element.
-
E.
frontType
Indicates the type or category of a front (e.g., boundary or leading side) that one entity presents or forms relative to another.
- F. None of above.
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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 21, 2026, 4:24 p.m.