Triple
T32181302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balingoan |
E821987
|
entity |
| Predicate | hasMaritimeTransport |
P76343
|
FINISHED |
| Object | roll-on/roll-off ferries |
—
|
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: roll-on/roll-off ferries | Statement: [Balingoan, hasMaritimeTransport, roll-on/roll-off ferries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaritimeTransport Context triple: [Balingoan, hasMaritimeTransport, roll-on/roll-off ferries]
-
A.
hasMaritimeConnection
chosen
Indicates a relationship in which an entity is linked to seas, oceans, or maritime activities, such as shipping, navigation, or coastal operations.
-
B.
isMaritimeRoute
Indicates that one location is connected to another by a navigable sea or ocean route used for maritime transport.
-
C.
hasFerryComponent
Indicates that something includes or is associated with a ferry-related part, feature, or segment within its structure or operation.
-
D.
hasSeaRouteConnection
Indicates that there exists a navigable maritime route linking two locations or entities.
-
E.
hasMaritimeFeature
Indicates that one entity possesses, contains, or is characterized by a maritime-related feature such as a sea, coast, harbor, or other oceanic element.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a007dd341108190a1d03eab46041694 |
completed | May 10, 2026, 12:45 p.m. |
| PD | Predicate disambiguation | batch_6a007b1fe2a881909ec50a1e65e4651b |
completed | May 10, 2026, 12:33 p.m. |
Created at: May 1, 2026, 12:34 a.m.