Triple
T29826092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chin-chin Yap |
E757380
|
entity |
| Predicate | subjectOfWorkHumanFlow |
P7040
|
FINISHED |
| Object | global refugee crisis |
—
|
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: global refugee crisis | Statement: [Chin-chin Yap, subjectOfWorkHumanFlow, global refugee crisis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectOfWorkHumanFlow Context triple: [Chin-chin Yap, subjectOfWorkHumanFlow, global refugee crisis]
-
A.
subjectOfWork
chosen
Indicates that one entity is the main topic, focus, or theme that a particular work (such as a book, article, or artwork) is about.
-
B.
workMovement
Indicates a relationship where an entity’s work or employment involves changing physical locations, such as traveling or relocating as part of their job.
-
C.
subjectOfDirection
Indicates that an entity is the target or recipient of a direction, instruction, or command issued by another entity.
-
D.
fieldOfWork
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
E.
subjectMovement
Indicates that the subject changes its position or location, capturing the action or process of moving.
- 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_69f22457c84c8190a6d9f56bc74082a9 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: April 29, 2026, 5:32 p.m.