Triple
T33713916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opera Ads |
E863817
|
entity |
| Predicate | notableRegionPresence |
P39809
|
FINISHED |
| Object | Africa |
E1402
|
NE 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: Africa | Statement: [Opera Ads, notableRegionPresence, Africa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRegionPresence Context triple: [Opera Ads, notableRegionPresence, Africa]
-
A.
notablePresence
Indicates that an entity has a significant or prominent presence in relation to another entity, context, or domain.
-
B.
notableAreaWithin
Indicates that one area is a particularly significant or noteworthy part located inside another, larger area.
-
C.
hasNotabilityRegion
Indicates that an entity’s notability, prominence, or recognition is specifically associated with a particular geographic region.
-
D.
observedInRegion
Indicates that something has been detected, recorded, or seen occurring within a specified geographic or spatial region.
-
E.
notableInRegion
chosen
Indicates that an entity is recognized as notable, prominent, or significant within a specified geographic region.
- F. None of above.
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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a365c66df1481908ad93dc5ac672af1 |
completed | June 20, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:44 a.m.