Triple
T16900927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Novia de Honduras |
E424431
|
entity |
| Predicate | refersToCityRole |
P86374
|
FINISHED |
| Object | major Caribbean port of Honduras |
—
|
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: major Caribbean port of Honduras | Statement: [La Novia de Honduras, refersToCityRole, major Caribbean port of Honduras]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToCityRole Context triple: [La Novia de Honduras, refersToCityRole, major Caribbean port of Honduras]
-
A.
hasCityRole
Indicates that an entity holds or is assigned a specific role, function, or status within a particular city.
-
B.
refersToCityAs
chosen
Indicates that one entity designates, mentions, or identifies another entity specifically as a city.
-
C.
refersToCityOn
Indicates that one entity makes reference to, or is specifically about, a particular city located on a given date or temporal context.
-
D.
focusCityRole
Indicates that a city serves a particular primary role or function within a broader geographic or organizational context.
-
E.
endpointCityRole
Indicates the role or function that a city plays as an endpoint within a route, connection, or network.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8dc7cf08190ad935935d8daf1d0 |
completed | April 18, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.