Triple
T29389111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESP Print Pro |
E745328
|
entity |
| Predicate | developerHeadquartersCountry |
P12991
|
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: [ESP Print Pro, developerHeadquartersCountry, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developerHeadquartersCountry Context triple: [ESP Print Pro, developerHeadquartersCountry, United States]
-
A.
organizationHeadquarteredInCountry
Indicates that an organization’s main headquarters or principal place of business is located within a specified country.
-
B.
countryOfHeadquartersOfEmployer
chosen
Indicates the country where the employing organization’s main headquarters is located.
-
C.
hasHeadquartersOn
Indicates that an organization’s main headquarters is located on a specified street, road, or similar thoroughfare.
-
D.
countryOfUnderlyingCompany
Indicates the country in which the underlying company associated with an entity is legally established or primarily based.
-
E.
acquiredCompanyCountry
Indicates the country in which the company that was acquired is located.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 28, 2026, 2:41 p.m.