Triple
T9365854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Al Hoceima |
E225396
|
entity |
| Predicate | isImportantHubFor |
P2958
|
FINISHED |
| Object | Riffian population |
—
|
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: Riffian population | Statement: [Al Hoceima, isImportantHubFor, Riffian population]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isImportantHubFor Context triple: [Al Hoceima, isImportantHubFor, Riffian population]
-
A.
isITHubOf
Indicates that an entity serves as a central location or primary center for IT-related activities, services, or operations for another entity or area.
-
B.
primaryHubFor
chosen
Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
-
C.
isMajorHubInCountry
Indicates that a location functions as a primary or central hub within a specified country, typically in terms of transport, commerce, or connectivity.
-
D.
locatedInHubOf
Indicates that one entity is situated within the central hub or core area associated with another entity.
-
E.
isMajorHubType
Indicates that an entity functions as a primary or central hub within a larger network or system.
- 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_69ca842cbddc819099d71ecec48cf9e5 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5041261c81909edab3b7fcd1fe22 |
completed | April 1, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69cc7a6abb8c81908c7a2f4ee92cc949 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:43 p.m.