Triple
T28341002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jinan University |
E717809
|
entity |
| Predicate | specialMission |
P22637
|
FINISHED |
| Object | education for overseas Chinese |
—
|
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: education for overseas Chinese | Statement: [Jinan University, specialMission, education for overseas Chinese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specialMission Context triple: [Jinan University, specialMission, education for overseas Chinese]
-
A.
publicMission
Indicates that an entity carries out a mission or activity intended for the general public or serving public interests.
-
B.
typeOfMission
chosen
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
C.
tertiaryMission
Indicates a relationship where an entity has a third-level or lower-priority mission or objective in addition to its primary and secondary missions.
-
D.
enabledMission
Indicates that a mission has been activated or made available for execution or participation.
-
E.
segmentMission
Indicates that a specific mission is associated with, assigned to, or carried out within a particular segment or phase.
- 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 12:39 a.m.