Triple
T396263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guayaquil |
E8988
|
entity |
| Predicate | hasPortActivity |
P4153
|
FINISHED |
| Object | container shipping |
—
|
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: container shipping | Statement: [Guayaquil, hasPortActivity, container shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortActivity Context triple: [Guayaquil, hasPortActivity, container shipping]
-
A.
hasMajorPort
Indicates that a location possesses a primary, significant seaport used for major commercial or transportation activities.
-
B.
hasKeyActivity
chosen
Indicates that an entity is associated with or performs a primary or central activity.
-
C.
hasPortico
Indicates that one entity (typically a building or structure) features a portico as part of its architectural design.
-
D.
hasConnection
Indicates that there exists a link, association, or relationship between two entities.
-
E.
hasInteraction
Indicates that there is some form of interaction or mutual action occurring between the related entities.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec8a941081909a152fda0ce24a98 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96bd3848190a66ca14dfbd26da5 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.