Triple
T35980691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estrella Fluvial de Inírida |
E1040553
|
entity |
| Predicate | hasMainAccessTown |
P22318
|
FINISHED |
| Object | Inírida |
E692865
|
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: Inírida | Statement: [Estrella Fluvial de Inírida, hasMainAccessTown, Inírida]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainAccessTown Context triple: [Estrella Fluvial de Inírida, hasMainAccessTown, Inírida]
-
A.
hasAccessToTown
Indicates that one entity is permitted or able to enter, use, or otherwise access a particular town.
-
B.
hasTown
Indicates that one entity possesses, contains, or is associated with a town as part of its structure, jurisdiction, or composition.
-
C.
majorAccessTown
chosen
Indicates that a location serves as a primary or significant access point to a town, such as a main route, gateway, or connection hub.
-
D.
hasTownship
Indicates that one administrative area or jurisdiction includes or is associated with a specific township.
-
E.
hasTownStatus
Indicates that an entity possesses the legal or administrative status of being recognized as a town.
- F. None of above.
Provenance (4 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a030e31e01881909c6032532cd3c31a |
completed | May 12, 2026, 11:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38bfe65828819086a5f22a8a5c204d |
completed | June 22, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_6a030dadea008190abe0a5652784bdd6 |
completed | May 12, 2026, 11:23 a.m. |
Created at: May 3, 2026, 4:07 p.m.