Triple
T36705129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maya |
E906335
|
entity |
| Predicate | hasMainPortFunction |
P201805
|
FINISHED |
| Object | passenger transport |
—
|
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: passenger transport | Statement: [Maya, hasMainPortFunction, passenger transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainPortFunction Context triple: [Maya, hasMainPortFunction, passenger transport]
-
A.
hasMajorPortFunction
chosen
Indicates that an entity serves as a primary port facility, playing a significant role in maritime transport, trade, or logistics operations.
-
B.
hasPortFunctionVia
Indicates that an entity possesses a port or interface that fulfills a specific function by means of, or through, another related element or mechanism.
-
C.
hasMajorPort
Indicates that a location possesses a primary, significant seaport used for major commercial or transportation activities.
-
D.
hasMainPortal
Indicates that one entity serves as the primary or main portal (entry point or access interface) for another entity.
-
E.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a034af7066c81908719bff353d77b16 |
completed | May 12, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_6a034a2fc2308190b0b8fbd458a39323 |
completed | May 12, 2026, 3:41 p.m. |
Created at: May 3, 2026, 4:12 p.m.