Triple
T33084867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Executive Officer of Montgomery Ward |
E846609
|
entity |
| Predicate | appliesToOrganizationFoundedIn |
P148489
|
FINISHED |
| Object | 1872 |
—
|
LITERAL 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: 1872 | Statement: [Chief Executive Officer of Montgomery Ward, appliesToOrganizationFoundedIn, 1872]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToOrganizationFoundedIn Context triple: [Chief Executive Officer of Montgomery Ward, appliesToOrganizationFoundedIn, 1872]
-
A.
refersToOrganizationBasedIn
Indicates that one entity makes reference to an organization whose primary location or headquarters is in a specified place.
-
B.
parentOrganizationFoundedIn
Indicates that the parent organization of an entity was established in a specified year or time period.
-
C.
hasUnderlyingFoundedInYear
chosen
Indicates that one entity has an underlying entity that was founded in a specified year.
-
D.
governsOrganizationFoundedIn
Indicates that a governing entity exercises authority over an organization that was established in a specified time or place.
-
E.
foundedAfter
Indicates that one entity was founded at a later time than another entity.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef112398081909237c3872345968b |
completed | May 9, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69feefb14ec08190ab401987d8c84a23 |
completed | May 9, 2026, 8:26 a.m. |
Created at: May 1, 2026, 1:26 a.m.