Triple
T23799170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Benoni |
E588621
|
entity |
| Predicate | isMainExitPointFor |
P79211
|
FINISHED |
| Object | Camiguin Island |
—
|
NE NERFINISHED |
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: Camiguin Island | Statement: [Port of Benoni, isMainExitPointFor, Camiguin Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMainExitPointFor Context triple: [Port of Benoni, isMainExitPointFor, Camiguin Island]
-
A.
isMajorExitOf
chosen
Indicates that one location serves as a primary or significant exit point from another location or route.
-
B.
hasExitFor
Indicates that something provides or includes a specific exit intended for a particular destination, purpose, or user.
-
C.
hasNumberedExit
Indicates that an entity (such as a road or highway) includes or is associated with an exit that has an assigned number.
-
D.
hasNumberOfExits
Indicates the relationship that specifies how many exits are associated with a given entity.
-
E.
isMainArrivalPointFor
Indicates that a location serves as the primary arrival point for a given entity or flow of 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6dfaae081908be48fa89e625f71 |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:51 p.m.