Triple
T28714359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weihsien |
E729916
|
entity |
| Predicate | campOpened |
P165251
|
FINISHED |
| Object | 1943 |
—
|
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: 1943 | Statement: [Weihsien, campOpened, 1943]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: campOpened Context triple: [Weihsien, campOpened, 1943]
-
A.
isOpeningFor
Indicates that one entity serves as the beginning, introduction, or initial act for another entity, such as an event, performance, or sequence.
-
B.
hallOpenedIn
Indicates that a particular hall began operating or was officially opened in a specified time or event.
-
C.
homeVenueOpened
Indicates that a venue has officially begun operating as the designated home location for a particular team or organization.
-
D.
mainVenueOpened
Indicates that the primary venue associated with an event or organization has begun operations or officially opened.
-
E.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
- F. None of above. chosen
Provenance (4 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 28, 2026, 5:50 a.m.