Triple
T19717687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 香港中文大学工程学院创院院长 |
E473521
|
entity |
| Predicate | 创立背景 |
P130309
|
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.
hasCauseOfEstablishment
chosen
Indicates that an entity was established or founded as a result of a specified cause, reason, or initiating circumstance.
-
B.
inceptionOfOrganization
Indicates that an event, action, or point in time marks the founding or formal beginning of an organization.
-
C.
organizationFounded
Indicates that an organization was established or created at a specific point in time, often by a particular founder or founding entity.
-
D.
foundedOnOccasionOf
Indicates that something was established or created specifically in response to, or to mark, a particular event or occasion.
-
E.
organizationTypeFounded
Indicates the type or category of organization that was established or created in a founding event.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6440ec9e881909b75c0ebefab827f |
completed | April 20, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.