Triple
T35719554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aguadillana |
E1032432
|
entity |
| Predicate | hasRootToponym |
P97773
|
FINISHED |
| Object | Aguadilla |
—
|
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: Aguadilla | Statement: [Aguadillana, hasRootToponym, Aguadilla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRootToponym Context triple: [Aguadillana, hasRootToponym, Aguadilla]
-
A.
hasOriginToponym
chosen
Indicates that something originates from, or is derived from, the place denoted by a specific toponym (geographical name).
-
B.
hasNotableToponym
Indicates that an entity is associated with a place name that is particularly notable, distinctive, or significant.
-
C.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of another entity.
-
D.
hasCanonicalToponym
Indicates that an entity is associated with its standard or officially recognized place name.
-
E.
includesToponym
Indicates that one entity contains or references a place name (toponym) associated with another entity.
- 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: May 3, 2026, 4:05 p.m.