Triple
T37016731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johannesburg |
E916101
|
entity |
| Predicate | countryBred |
P204197
|
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: [Johannesburg, countryBred, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryBred Context triple: [Johannesburg, countryBred, United States]
-
A.
country1
Indicates that the subject entity is a country (or represents a country) in the given context.
-
B.
country2
Indicates a secondary or alternative country associated with an entity, such as a second nationality, location, or jurisdiction.
-
C.
countryIn
Indicates that one entity is geographically or politically located within the boundaries of a specified country.
-
D.
countryOn
Indicates that one country is located on or occupies the territory of another geographic entity (such as a larger region, continent, or island).
-
E.
countryDuring
Indicates that one entity exists, occurs, or is valid within the temporal span during which the other entity is recognized as a specific country.
- F. None of above. chosen
Provenance (5 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_69f76e920dc48190acb6bb7ebc4dffab |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a03460f3a8c8190ae3f4cd69e0e54d9 |
completed | May 12, 2026, 3:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3f69f94ec08190944b30ae0343d3aa |
completed | June 27, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_6a0345810b3481908aec06ab2b712e12 |
completed | May 12, 2026, 3:21 p.m. |
| PDg | Predicate description generation | batch_6a03460e44cc8190b1ac3e8ac0840a52 |
completed | May 12, 2026, 3:23 p.m. |
Created at: May 3, 2026, 4:14 p.m.