Triple
T25150442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Best First Book |
E630059
|
entity |
| Predicate | hasNotableRegionCategories |
P131006
|
FINISHED |
| Object | Africa |
—
|
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: Africa | Statement: [Best First Book, hasNotableRegionCategories, Africa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableRegionCategories Context triple: [Best First Book, hasNotableRegionCategories, Africa]
-
A.
hasNotabilityCategory
Indicates that an entity is associated with a particular category that characterizes its type or area of notability.
-
B.
hasNotableUsageRegion
Indicates that something is prominently or distinctively used within a particular geographic region.
-
C.
hasNotabilityRegion
chosen
Indicates that an entity’s notability, prominence, or recognition is specifically associated with a particular geographic region.
-
D.
hasCategories
Indicates that an entity is associated with one or more categories that classify or group it.
-
E.
hasNotableCollectionArea
Indicates that an entity possesses a significant or distinguished collection focused on a particular subject, theme, or domain.
- 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 18, 2026, 6:30 a.m.