Triple
T38325084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 北海公园 |
E1036760
|
entity |
| Predicate | 历史类型 |
P66217
|
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.
歴史
Indicates a relationship where something pertains to, records, or is involved in the events, development, or study of the past over time.
-
B.
historicalType
chosen
Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical context.
-
C.
historicalGenre
Indicates that something belongs to or is categorized within a particular historical genre.
-
D.
historicalCategory
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
-
E.
historicalDiscipline
Indicates that one entity is a field or branch of academic study within the broader domain of history in relation to another entity.
- 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_69f76e1c16fc8190bde982289dd5106b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.