Triple
T35986250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prime (Counterpart) |
E1040717
|
entity |
| Predicate | isFromWorkCountryOfOrigin |
P171214
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [Prime (Counterpart), isFromWorkCountryOfOrigin, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFromWorkCountryOfOrigin Context triple: [Prime (Counterpart), isFromWorkCountryOfOrigin, United States]
-
A.
isFromWorkCountry
chosen
Indicates that an entity originates from or is associated with the country where another entity works.
-
B.
basedOnWorkCountryOfOrigin
Indicates that something is determined or derived from the country of origin of a work.
-
C.
fromWorkCountryOfOrigin
Indicates that something originates from the same country as the subject’s place of work.
-
D.
isOccupationalInOrigin
Indicates that something (typically a name or term) originates from or is derived from an occupation or profession.
-
E.
associatedWorkCountryOfOrigin
Indicates that the related work originates from, or is primarily associated with, a specified country.
- 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.