Triple
T10035428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 沙面岛 |
E204952
|
entity |
| Predicate | 历史事件 |
P2107
|
FINISHED |
| Object | 曾为英法租界所在地 |
—
|
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: 曾为英法租界所在地 | Statement: [沙面岛, 历史事件, 曾为英法租界所在地]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 历史事件 Context triple: [沙面岛, 历史事件, 曾为英法租界所在地]
-
A.
hasHistoricalEvent
chosen
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
B.
politicalHistory
Indicates that there exists a historical political relationship, involvement, or background connecting the entities, such as past offices held, affiliations, or political events linking them.
-
C.
historicActivity
Indicates that an entity engaged in an activity or event of historical significance in the past.
-
D.
historicalFocus
Indicates that something is primarily concerned with, centered on, or devoted to a particular historical period, event, or theme.
-
E.
historicalCategory
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdce4a515c8190baec86d924623b12 |
completed | April 2, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:55 p.m.