Triple

T34105567
Position Surface form Disambiguated ID Type / Status
Subject Mpongwe people E874696 entity
Predicate portCityAssociation P2745 FINISHED
Object Libreville 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: Libreville | Statement: [Mpongwe people, portCityAssociation, Libreville]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: portCityAssociation
Context triple: [Mpongwe people, portCityAssociation, Libreville]
  • A. isPortOf
    Indicates that one location or facility serves as a port or harbor for another place, entity, or transportation route.
  • B. isAmongLargestPortsIn
    Indicates that a port ranks among the largest ports within a specified geographic or administrative area.
  • C. cityAssociatedWith
    Indicates that there is a notable connection or relationship between a city and another entity, such as relevance, involvement, or contextual association.
  • D. isPortOfCallFor
    Indicates that a location serves as a scheduled stop or destination for a ship, vehicle, or journey.
  • E. hasPortCity chosen
    Indicates that a place or region possesses or is associated with a city that functions as its port.
  • 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_69f349a80d4481908527317d43f5c579 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f70ca987dc81908adb7451a3e2c20f completed May 3, 2026, 8:51 a.m.
PD Predicate disambiguation batch_69f70ac0170c819098e3b8e41d02efef completed May 3, 2026, 8:43 a.m.
Created at: May 1, 2026, 1:53 a.m.