Triple
T29007612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black International |
E736477
|
entity |
| Predicate | notableCountryOfActivity |
P6230
|
FINISHED |
| Object | United States |
E14
|
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: United States | Statement: [Black International, notableCountryOfActivity, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCountryOfActivity Context triple: [Black International, notableCountryOfActivity, United States]
-
A.
notableCountry
chosen
Indicates that a country holds particular significance or prominence in relation to the subject entity.
-
B.
notableYearOfActivity
Indicates the specific year during which an entity was particularly active, prominent, or notable in its activities or impact.
-
C.
notableCountrySection
Indicates that a specific section or part of a country is particularly notable or significant in some context.
-
D.
notableProjectCountry
Indicates that a country is associated with a notable project undertaken by the subject.
-
E.
notableHolderCountry
Indicates that a country is recognized as a significant or notable holder of a particular item, title, record, or distinction.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a01d9ca07b88190b4ad70b6336447b6 |
completed | May 11, 2026, 1:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25058fc2b08190a6d11785d5e9fd2b |
completed | June 7, 2026, 5:45 a.m. |
| PD | Predicate disambiguation | batch_6a01d807c3048190b79f0b6b933dd3b7 |
completed | May 11, 2026, 1:22 p.m. |
Created at: April 28, 2026, 9:39 a.m.