Triple
T8077629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanghai Race Club |
E188530
|
entity |
| Predicate | statusAfter1949 |
P75256
|
FINISHED |
| Object | repurposed by authorities of the People's Republic of China |
—
|
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: repurposed by authorities of the People's Republic of China | Statement: [Shanghai Race Club, statusAfter1949, repurposed by authorities of the People's Republic of China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfter1949 Context triple: [Shanghai Race Club, statusAfter1949, repurposed by authorities of the People's Republic of China]
-
A.
after1949
chosen
Indicates that one event, state, or fact occurs or becomes true after the year 1949.
-
B.
locationAfter1949
Indicates that the specified location is relevant, valid, or applicable only for the time period after the year 1949.
-
C.
statusAfter1956
Indicates the status or condition of an entity as it existed at any time after the year 1956.
-
D.
statusAfter1979
Indicates the status or condition of an entity specifically in the period following the year 1979.
-
E.
statusAfter1946
Indicates the status or condition of an entity as it existed after the year 1946.
- 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_69ca82b50c708190863f661d438e68df |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb40a184488190b19ef7066f0f5057 |
completed | March 31, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:28 p.m.