Triple
T9561631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Munji |
E230686
|
entity |
| Predicate | hasVitalityTrend |
P5318
|
FINISHED |
| Object | declining intergenerational transmission |
—
|
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: declining intergenerational transmission | Statement: [Munji, hasVitalityTrend, declining intergenerational transmission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVitalityTrend Context triple: [Munji, hasVitalityTrend, declining intergenerational transmission]
-
A.
hasTrend
chosen
Indicates that something exhibits or is associated with a particular pattern of change or direction over time.
-
B.
hasTendency
Indicates that an entity is inclined or likely to exhibit a particular behavior, characteristic, or outcome under certain conditions.
-
C.
hasRevitalizationMovement
Indicates that there exists an organized effort or movement aimed at renewing, restoring, or reinvigorating the subject entity.
-
D.
healthIndicator
Indicates a measure or signal that reflects the health status or condition of an entity.
-
E.
hasTreeVigor
Indicates the assessed strength, health, and growth potential of a tree in relation to its current condition or environment.
- 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd994d31e08190b139f5ad10d8ea31 |
completed | April 1, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:03 p.m.