Triple
T8015080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hillsboro Hops |
E186591
|
entity |
| Predicate | primaryAffiliationStartYear |
P38522
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Hillsboro Hops, primaryAffiliationStartYear, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAffiliationStartYear Context triple: [Hillsboro Hops, primaryAffiliationStartYear, 2013]
-
A.
affiliationStart
chosen
Indicates the point in time when an entity’s formal association or membership with another entity begins.
-
B.
primaryAffiliation
Indicates the main organization, institution, or group with which an entity is chiefly associated or formally connected.
-
C.
modernAffiliation
Indicates a current or contemporary organizational, institutional, or group association between entities, as opposed to a historical or past affiliation.
-
D.
laterAffiliation
Indicates that an entity becomes affiliated with another entity at a later time than a previously mentioned or initial affiliation.
-
E.
conferenceAffiliationStart
Indicates the point in time when an entity’s affiliation with a particular conference begins.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3df24e4c8190ae1c46e97e54787d |
completed | March 31, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69cb048c9f488190b4fb8917a9c21bc5 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:20 p.m.