Triple
T7344968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muna language |
E169352
|
entity |
| Predicate | hasMajorCityOfUse |
P76704
|
FINISHED |
| Object | Raha |
—
|
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: Raha | Statement: [Muna language, hasMajorCityOfUse, Raha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorCityOfUse Context triple: [Muna language, hasMajorCityOfUse, Raha]
-
A.
hasMajorCity
Indicates that a location possesses at least one city of significant size, importance, or influence within its region or country.
-
B.
hasMajorCityOnRoute
Indicates that a major city lies along, or is directly served by, a specified route or path between locations.
-
C.
hasMajorCityHub
Indicates that an entity contains or is associated with a primary, high-importance city that functions as a central hub for activity, services, or connectivity.
-
D.
isMajorCityIn
Indicates that a city is a primary or significant urban center located within a specified larger region or country.
-
E.
hasMajorCityRole
Indicates that an entity plays a significant official or functional role in the governance, administration, or key operations of a major city.
- F. None of above. chosen
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_69c68a57710481909f0c1f3c6ebdb6f2 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f139505c8190a7158cf59a6e089e |
completed | March 27, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69c6f02aeeb8819099d1626566cec18b |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f1379cac81908b35e617c44c7b13 |
completed | March 27, 2026, 9:05 p.m. |
Created at: March 27, 2026, 3:05 p.m.