Triple
T15718171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gyali |
E381013
|
entity |
| Predicate | hasAccessPort |
P34282
|
FINISHED |
| Object | small port for pumice loading |
—
|
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: small port for pumice loading | Statement: [Gyali, hasAccessPort, small port for pumice loading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessPort Context triple: [Gyali, hasAccessPort, small port for pumice loading]
-
A.
hasNearbyPortAccess
Indicates that an entity is located close enough to a port to feasibly use it for access or transport.
-
B.
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).
-
C.
hasPortConnection
Indicates that one entity is linked to another via a port or interface through which data, power, or signals can be transmitted.
-
D.
hasAccessMethod
Indicates that one entity uses or is associated with a particular method or mechanism for accessing another entity or resource.
-
E.
hasPorts
chosen
Indicates that an entity is equipped with or provides access points (ports) for connection, communication, or interface with other entities or systems.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f932a248190b65ecfb2bc56e715 |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:45 a.m.