Triple
T3738852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evergrande Group |
E79649
|
entity |
| Predicate | hasCrisis |
P25894
|
FINISHED |
| Object | Evergrande liquidity 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: Evergrande liquidity crisis | Statement: [Evergrande Group, hasCrisis, Evergrande liquidity crisis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCrisis Context triple: [Evergrande Group, hasCrisis, Evergrande liquidity crisis]
-
A.
hasDisaster
Indicates that an entity experiences, is affected by, or is associated with a disaster event.
-
B.
crisisRelatedTo
chosen
Indicates a relationship where one situation, event, or condition is connected to, associated with, or relevant to a crisis.
-
C.
majorCrisis
Indicates a severe, high-impact crisis or emergency situation affecting an entity or system.
-
D.
hasTragicPast
Indicates that an entity has experienced a significantly sorrowful or traumatic history that influences its present state or characterization.
-
E.
hasDam
Indicates that a watercourse, reservoir, or similar feature is impounded or controlled by a specific dam.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb404b908190b6b4ee583dee3cc9 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc048f28c819092bed16a95a3cac1 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.