Triple
T22703603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taiwan Provincial Government |
E561385
|
entity |
| Predicate | statusAfterStreamlining |
P127
|
FINISHED |
| Object | nominal existence with minimal staff |
—
|
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: nominal existence with minimal staff | Statement: [Taiwan Provincial Government, statusAfterStreamlining, nominal existence with minimal staff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfterStreamlining Context triple: [Taiwan Provincial Government, statusAfterStreamlining, nominal existence with minimal staff]
-
A.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
B.
status
chosen
Indicates the current condition, state, or standing of an entity within a given context.
-
C.
complexityStatus
Indicates the current level or state of complexity associated with an entity or process.
-
D.
stabilizationOutcome
Indicates the result or state achieved after a stabilization process has been applied to something.
-
E.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178cca1e48190bbe7910f13692803 |
completed | April 29, 2026, 3:19 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:16 p.m.