Triple
T12099510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eti-Osa |
E288153
|
entity |
| Predicate | hostsFunction |
P2592
|
FINISHED |
| Object | major commercial hub of Lagos |
—
|
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: major commercial hub of Lagos | Statement: [Eti-Osa, hostsFunction, major commercial hub of Lagos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsFunction Context triple: [Eti-Osa, hostsFunction, major commercial hub of Lagos]
-
A.
houseFunction
Indicates the functional role or primary use that a house serves (e.g., residential, commercial, mixed-use).
-
B.
host
chosen
Indicates that one entity provides space, resources, or services to accommodate, receive, or entertain another entity.
-
C.
hostsBody
Indicates that one entity serves as the physical container or location in which another entity resides or is situated.
-
D.
homeFunction
Indicates that something serves as the primary place where an entity lives, resides, or is based.
-
E.
hostNOC
Indicates that one entity operates as the Network Operations Center (NOC) responsible for monitoring, managing, or supporting another entity’s network or services.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9178ad99c8190a54777b9bbe998bc |
completed | April 10, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69d915000454819089fee00022055599 |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.