Triple
T29787015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People's Republic of China in diplomatic talks |
E756290
|
entity |
| Predicate | oftenHeldAt |
P174643
|
FINISHED |
| Object | Great Hall of the People |
—
|
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: Great Hall of the People | Statement: [People's Republic of China in diplomatic talks, oftenHeldAt, Great Hall of the People]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenHeldAt Context triple: [People's Republic of China in diplomatic talks, oftenHeldAt, Great Hall of the People]
-
A.
typicallyHeldIn
Indicates that an event, activity, or process most commonly or usually takes place within a particular location, venue, or context.
-
B.
oftenHeldOn
Indicates that an event or activity typically takes place on a particular date, day, or time.
-
C.
oftenHeldAs
Indicates that one entity is frequently regarded, considered, or believed to be in a particular way with respect to another entity or property.
-
D.
oftenHeldWith
Indicates that one entity is frequently possessed, carried, or kept together with another entity at the same time.
-
E.
areHeldAt
chosen
Indicates that events or activities take place or occur at a specific location or venue.
- 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_69f22451fb748190bbdbab401280affb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 29, 2026, 5:09 p.m.