Triple
T34093795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toledo, Cebu |
E874367
|
entity |
| Predicate | hasRegularFerryService |
P1737
|
FINISHED |
| Object | Negros Island |
E104739
|
NE 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: Negros Island | Statement: [Toledo, Cebu, hasRegularFerryService, Negros Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegularFerryService Context triple: [Toledo, Cebu, hasRegularFerryService, Negros Island]
-
A.
hasFerryService
chosen
Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
-
B.
hasFerryPort
Indicates that a place serves as a location where ferries regularly dock to load and unload passengers or cargo.
-
C.
hasFerryComponent
Indicates that something includes or is associated with a ferry-related part, feature, or segment within its structure or operation.
-
D.
hasFerryType
Indicates that an entity (such as a ferry route or service) is associated with a specific type or category of ferry.
-
E.
isOneOfMainCarFerryRoutesTo
Indicates that something serves as one of the primary car ferry routes leading to a specified destination.
- F. None of above.
Provenance (4 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36d5c452708190a1f9b05a438c2ffd |
completed | June 20, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:52 a.m.